-
-
Notifications
You must be signed in to change notification settings - Fork 197
Stuck at "Restarting application on device" on Windows 10, iPad mini 2, compiled with NativeScript Sidekick cloud service. #5020
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Hi @bbc91,
The cause for this is It is expected that on Windows, Sidekick is unable to start the application on the device. LiveSync however should update the application after the application is started manually. Let me know if the issue persists after solving the Webpack compilation error. |
The problem still stays, but I think you should see, the whole log of building, because there is some warning I do not understand.
|
Hi @bbc91, As for the Webpack error, there seems to be a wrong require/import statement in I guess that you should update the path to '../../services/convertToJsonThenToObject', but it is better to check it as I am not familiar with the project structure. |
When I work on the same app, on Android device, when the build is complete, the app is installed on the Android device and opens automatically after the message on the console: "Restarting application on device". On iOS device, after this message, the app is not started automatically, I can start it with clicking on the icon of the app on the device. When I change code in a .Vue file, on Android device it is rebuild and LiveSynced and after the message "Restarting application on device", the app is refreshed on the android device and the changes are applied. On iOS device, after a change in a .Vue file, the project is also rebuild and there is a message on the console "Restarting application on device", but nothing happens on the device. I have to close the Nativescript Sideckick and wait 5 minutes to build the whole project again and start it on the device. This is the 2 problems preventing me for developing, because of waiting. The android development was fast, because I didn't had this issue. The difference is that I'm building the app locally for android, but on the cloud for iOS. As I said, I tried this morning with FRESH installed Nativescript Vue project, and the issues are the same. |
Hi @bbc91 , As a temporary workaround you can install NativeScript 6.0.3 and use the CLI cloud commands, because Sidekick requires higher version of NativeScript. You can use the following commands: |
Thank you for your help! I much appreciate it! Best regards, Georgi Ivanov. |
Hi @bbc91, |
Hello, same probem here... And when using the version 6.0.3 we can't use iPhone device running under iOS 13 (Error is: Could not start service com.apple.mobile.house_arrest.). Thank you |
…hile stopping the application Currently when the application is stopped, NativeScript CLI hangs up on "Restarting application". This happens as we're no able to start `gdb server` due to some error. (for example, not mounted developer disk image on device). In this situation, `ios-device-lib` doesn't print any message back to the CLI and this way the entire `tns run` command is blocked. Printing error in this situation will ensure that NativeScript CLI will continue the command execution. Rel to NativeScript/nativescript-cli#5020
…hile stopping the application Currently when the application is stopped, NativeScript CLI hangs up on "Restarting application". This happens as we're no able to start `gdb server` due to some error. (for example, not mounted developer disk image on device). In this situation, `ios-device-lib` doesn't print any message back to the CLI and this way the entire `tns run` command is blocked. Printing error in this situation will ensure that NativeScript CLI will continue the command execution. Rel to NativeScript/nativescript-cli#5020
same problem here. Using version 6.0.3 doesn't work either because of the house_arrest bug on iOS 11 + devices. |
It is expected to see the error for the house_arrest with NS 6.0.3 as it it is fixed in v6.1.0. However, the fixes for both issues (the current one and house_arrest) should be available in the Let us know if the issue is resolved on your side. |
running npm i -g nativescript@next didn't fix it for me. Afterwards I followed the upgrade guide and tried running 'tns upgrade next' which is giving me the following error:
|
problem is solved for me! In the end it had nothing to do with nativescript but with an out of date xcode version. Nativescript just didn't show that in the log (guess thats the fix in next?) anyways all good now. |
I'm glad your issue is resolved. Regarding to the error you mentioned, I verified it is a bug with latest version of NativeScript CLI and logged it as separate issue here. |
Environment
Describe the bug
I'm developing an iOS app for iPad using NativeScript Sidekick for building the app on the cloud and hot reloading it on the device. The build is successful, but the console is stuck at "Restarting application on device". I can open the app from the icon, and it works, but when I make a change on the code, the app is rebuild on the cloud, then message on the console appears "Webpack build done" and again, nothing refreshes on the device, so I have to turn off the Sidekick and build all over again, and then open the app manually again. The development will take forever like this, so before continue I'm looking for a solution.
This is when build the app and where it stuck:
And this is when I make a code change:
Nothing happens on the device after. It is just stays with the previous version of the app and I have to restart the nativescript sidekick and build again so I can have the changes on the device.
To Reproduce
Build iOS app on the NativeScript Sideckick cloud.
Expected behavior
When the app is build and installed on the device, it should reload the app and open it, then on any change of code, after the fast rebuilding with hot module replacement it should refresh on the device with the new changes.
The text was updated successfully, but these errors were encountered: