Having a problem debugging Android and IOS using Ripple. I am using the Blank App(Apache Cordova) project with no changes.
Problem:
The first time I build the project and test with Ripple, Chrome and Ripple work correctly. Subsequent builds causes JavaScript breaks that block the app from running. When I F5 thru the breaks, the Ripple UI and App appear in Chrome.
Steps To Repeat:
Open my blank Cordova app.
Select Debug > Android > Ripple - Nexus 7.
Build the app by clicking on the green build button. App runs fine.
Close the browser and stop debugging
Build the app again by clicking on the green build button. App does not appear in Chrome.
JavaScript highlighted in yellow appears in the IDE.
Click F5 to continue through breaks. Ripple and App appears in Chrome when all breaks have been viewed.
Fix:
None.
I can Continue (F5) the scripts until the app and Ripple appears in Chrome. Closing the project and reopening it will allow the app to run properly, but the problems repeat when I debug the project after the 1st attempt.
This is a bug that will be fixed in the next update. See this post for a full explanation and suggested workaround.
Related
I am building an Ionic app, but once the page is getting bigger, the app presents an scroll, there is any way to remove the scroll and let the app more native like?
My code has only 2 slides with some products description and category.
"Ionic Lab" is a deprecated desktop application, sunsetted in 2016. the Ionic CLI command "ionic serve" lets you serve the app locally in a browser. So it appears you're previewing your application in a web browser. When doing this, it's not going to appear or behave exactly as it will on a real mobile device. If you run a build, open your app in Xcode and test in the iOS simulator, you'll most likely see that no scrollbar is visible.
Testing locally in a browser with ionic serve is very practical and useful but the preview should not be believed to be a 100% accurate native preview.
I've been trying to rework some pages that needed a change.
When I've edited a xaml page and corresponding xaml.cs page when Visual Studio built the page and ran it on the simulator it behaved like I did no change on it.
I've tried cleaning and building and cleaning and rebuilding my solution but to no avail.
There are some issues with running the simulator as well when sometimes it would start the app normally and the next time I start it I need to kill simulator completely and then re-run it
Is there some kind of setting that I've missed to set-up?
When you are making changes to xaml in debugging mode, you must hit save button to tell VS to push changes to emulator. The screenshot you provided clearly says that you didn't hit save. Also you must to enable hot reload for Xamarin. VS Options -> Xamarin -> Hot Reload.
Our test automation sometimes makes the simulator crash. In these cases, we often see the dialog below throw on the simulator's next launch. This modal UI dialog breaks automation by preventing application execution until the user chooses an action.
When the iOS Simulator crashes, the application state may be saved in ~/Library/Saved Application State/com.apple.iphonesimulator.savedState. The presence of this folder or values in the data within triggers the modal dialog.
Removing this folder (rm -rf "~/Library/Saved Application State/com.apple.iphonesimulator.savedState") before restarting iOS Simulator will prevent the dialog from appearing. This has been tested with iOS Simulator shipped in Xcode 9.4.1.
If I press the stop debugging button while debugging my ASP.NET Core app in Google Chrome it closes the Kestrel process window and the Chrome window that opens automatically on launching Debug. This is great and convenient!
Unfortunately it seems like Visual Studio closing Chrome in this way confuses Chrome and makes it think it has crashed. So every time I launch debugging in Visual Studio, a new Chrome window opens, and I see this annoying pop-up:
I found a similar issue brought up here, but it is for VS Code instead of VS2017. I don't think launch.json is a concept in VS2017 so I have no idea how to implement that workaround.
How can I prevent this from happening? Thanks!
Close all open Chrome windows
Edit file:
"%UserProfile%\AppData\Local\Google\Chrome\User Data\Default\Preferences"
Set:
"exit_type": "none"
and
"exited_cleanly":true
Change the Preferences file to readonly
Ive been trying to add a button to properly exit an Android app, built using Flex 4.6. I have used the command NativeApplication.nativeApplication.exit(); which seems to work on the emulator, and kills off the emulator.
When I run it on a device, it doesnt exit, it actually seems to go to start of the app (my login screen) which is kinda strange.
I hypothesise that something system-wide is holding the app in process or re-starting it. Anyone had any experience with this?
That code should work. I use it in my android flex app with no problem. The application quits correctly and I am dropped back at the home screen. What version of Android are you using? I was using 2.3 when I did this. If you have it running in debug mode, do you see any errors output to the console? Using the debugger will also allow you to see if it is not quitting properly or restarting on quit(you would see the splash screen again if this was the case)