Got an app and works on Android and iOS.
There's one particular page in the app when I visit crashes in the production version of iOS app. Works fine in the emulator, works on the device in debug mode.
I narrowed it down to nativescript-imagepicker plugin. Even though no plugin specific code is being executed when the page is opened - it crashes as long as include the plug-in and have the code in a function (not called). If I comment out the code (but still include the plugin) - that works also.
What could cause such a problem?
Does the NS back-end run some code if the plugin is referenced in the page file?
Again works fine in emulator on iOS and also when tested directly on the device.
The problem occurs when the app is downloaded from itunesconnect - so there's no way for me to test it - console messages etc.
Using NS 3.2 with nativescript-imagepicker 0.3.6.
Related
I've installed latest version on Nativescript as documentation says:
nativescript Full setup with javascript
Everything went fine, so next i did setup my first project: tns create HelloWorld
Next i started the project using npm run ios
Iphone emulator has started, and when i made first change to text label, i saw that app refresh, but on second change conosle said that project is refreshed, but no changes on app. If i close app and run again, i see live reload only works once and next it igores any changes. My question is how to fix this.
I am testing an iOS and Android Xamarin application using the Appium desktop tool (and therefore language agnostic). The application, when attempting to sign in, loads a webview. However, on both iOS and Android applications, Appium still sees the context as NATIVE_APP. I tried following the instructions here in case there was an issue with Appium desktop, but I got an array containing only NATIVE_APP when calling #driver.available_contexts (Ruby), so I don't believe that's the issue. I AM able to inspect the login page using Safari / Develop / Simulator, so I am unsure who Appium can't see the webview. Any help would be appreciated.
Note - I have another native application that uses the same login intercept webview, and appium DOES see the Webview. So it's entirely possible that this is related to Xamarin. But I have no way of knowing for certain
Can you check the below setup according to appium docs for android.
There is an additional step necessary within your app build, unfortunately. As described in the Android remote debugging docs it is necessary to set to true the setWebContentsDebuggingEnabled property on the android.webkit.WebView element.
Every time I run my Xamarin.iOS UITest, I get an error:
System.Exception : Unable to contact test backend running in app. A common cause is that the app is not properly linked with Calabash. Please verify that it includes the Calabash component.
But I don't want to connect to any test backend - I want to run it locally on my iPhone Simulator (I am on a Mac). I created a basic Xamarin project, added a UITest project, and am able to run Android with no issues. I did install the Xamarin.TestCloud.Agent package, and included the #if ENABLE_TEST_CLOUD block in AppDelegate.cs (just in case it was required for local testing), but I can't get it to run locally.
Interestingly, the simulator DOES load, and so does the app. But the test never actually starts (it will fail on .StartApp()). I also get the Mac alert 'Do you want the application "DeviceAgent-Runner.app" to accept incoming network connections?' to which I answer Allow, because why not.
I'm so confused...
Thanks!
edit: this is my app ConfigureApp code:
return ConfigureApp
.iOS
.Debug()
.AppBundle ("../../../Kroe761Test.iOS/bin/iPhoneSimulator/Debug/device-builds/iphone 11-13.5/kroe761.iOS.app")
.DeviceIdentifier("D68D731A-775F-4BF1-8EF6-13F3FEDD00CF") // iphone 11 pro
.StartApp();
I guess you missed adding ENABLE_TEST_CLOUD; in your project options.
Follow all the steps from here.
https://learn.microsoft.com/en-us/appcenter/test-cloud/uitest/get-started-xamarin-forms
Clean and build your project. It should be working.
The ios app was working fine and I was working and debugging on the simulator, suddenly the app starts and closes, no crash report. The app closes after loading the assembly as per what I can see from the application output log with no crash report. Even the debugger detaches and stopped debugging and comes to it default play state.
Lastly I also see the this error " The call is ambiguous between the calling methods App.InitializeComponent() and App.InitializeComponent(). Basically for all Xaml Pages.
I tried reinstalling all the packages and updating for all Packages(shared/ios/android) but still issue persist.
Screenshot of the package installed.
I have a perfectly working (Pebble Classic) app on the Pebble app store. However, when installed on Pebble Time, the JS is not always executed (or takes too long to kick in) and in the logs I can see "[PHONE] pebble-app.js:?: notifyWithAppMessage: no delegate."
Is it Aplite compatibility issue or do I need to do something differently for Basalt platform. App is SDK2, thus compiled only for Aplite.
Note that the JS was not bundled in iOS app yet, so if you want to try it you must use Android app.
https://apps.getpebble.com/applications/5541de234b4d965adb000050
This should work. Please file a bug via the mobile app.