I have been following this document to implement a hybrid webview and am running into an issue with the Target Android version. It states in the document:
On Android Oreo ensure that the Android manifest sets the Target
Android version to Automatic. Otherwise, running this code will result
in the error message "invokeCSharpAction is not defined".
I am using the Android 8.1 - API 27 simulator and I am getting that error. I tried to set the Target Android version to "Automatic" as it suggests in the Android Manifest portion of the project properties, but "Automatic" is not an option I can pick. The only option I get that isn't a specific version is "Use Compile using SDK Version" and that doesn't solve the problem. What am I missing?
Have you seen the following thread?
https://github.com/xamarin/xamarin-forms-samples/issues/343
It states that sample from the documentation does not work and needs to be changed according to the one posted in this thread. Please let me know if it helps or not.
Related
I have been dealing with the same issue for a few days now. I'm unable to upload any app store connect files due to the libAgoraRTMWrapper file. To be clear, this entire app has been built through Unity using agora SDK. The reason for failure, according to XCode, is that the wrapper "doesn't have the correct file type for this location". Invalid Swift support.
This leads me to wonder if the libagoraRTMWrapper is even necessary. Yes, I would like to keep using RTM but not at the expense of several build failures.
As a sidenote, XCode does mention that the build is being made for iOS but the wrapper was built for iOS + iOS simulator. I don't remember ever specifying that but it could just be the way the SDK was initially imported.
this library is necessary for RTM to work. Do you have a custom build setting for the project? It is verified that the included SDK Demo works on iOS builds. Perhaps you can build that and compare the build setting to yours to find out what went wrong?
I have an issue with running my JavaFX/Gluon Mobile App on iPadOS 13.3 Actually the similar issue is described here: Gluon sample application failing on ios devices I've identify that the problem is caused by RoboVM and should be fixed in the version 2.3.10-SNAPSHOT
How can I change the version of RoboVM used by Gluon? In the Gluon documentation is mentioned the ios gradle extension property robovmVersion. This property can be set to the version robovmVersion ='2.3.5-ios12' but not 2.3.10. The reason is that on the bintray there is no version 2.3.10.
Is there any way to force Gluon Mobile to use RoboVM 2.3.10?
This is a temporary solution until the JavaFXPorts repository gets updated. There seems to be an issue with iOS 13.3 and JavaFX native libraries that's why apps crash even when using the latest 2.3.10-SNAPSHOT.
The breaking line of code was identified yesterday by Demyan Kimitsa who suggested to remove assert from the following native class
GlassApplication.m:635
assert(pthread_key_create(&GlassThreadDataKey, NULL) == 0);
becomes
thread_key_create(&GlassThreadDataKey, NULL) == 0;
I have created a build with the above change in native libraries and with the use of RoboVM 2.3.10-SNAPSHOT everything runs normal again even in the latest iOS.
Now that the issue is identified, I believe it is a matter of time until a new JavaFXPorts fix is published.
If you can't wait, you can download the HelloWorld sample with the new binaries from here. Adjust the parameters in build.gradle and you are ready to go.
I have released my app a couple of times and had the process under control until most recently when I updated from XCode 9 to XCode 10 due to a 3rd party lib requirement.
Everything seems fine when I compile and run on the emulator; but, when I come to the "Validate" (Archive) the app prior to uploading to the app store I am getting an error.
My Setup:
MacOS 10.14.2 (Mojave)
Using XCode 10.1 (10B61)
Error message:
Missing entitlement. watchOS extension
'XXX.app/Watch/aw-xxx.app/PlugIns/aw-xxx Extension.appex' uses
'UIBackgroundModes' value 'workout-processing' without the required
entitlement 'com.apple.developer.healthkit' signed into the bundle.
Watch Extension Capabilities:
The app is built using cordova-8.1.1 and cordova-ios-4.5.5
cordova build ios --buildFlag='-UseModernBuildSystem=0'
In addition to that, the project on XCode 10 has been set to 'Legacy Build System' on File -> Project Settings.
Lastly, the 'aw-xxx Extension.entitlements' has the 'HealthKit' key value set to 'YES' under the 'aw-xxx Extension' folder as one could expect.
Any help or pointers would be much appreciated.
I'm happy to provide more info, logs, etc as well, thanks!
After following the comment below I managed to get my app to validate once again on XCode 10:
Hi #guikeller Just wondering if it is related. I had similar issue while doing a ionic cordova app release. I figured the
com.apple.developer.healthkit
is missing in my platforms/ios/myApp/Entitlements-Release.plist. It does exist in Entitlements-Debug.plist. All I did is copied the key from the debug file to release and app store accepted it.
Source: https://github.com/apache/cordova-ios/issues/475#issuecomment-450174628
In addition to that, I was also able to submit my app into the app store.
After changing to the SDK 4.8 (all other files remain unchanged) the build fails if minify is enabled. The error is String-index overflow.
Is there an updated proguard-rules file for 4.8 that takes into account new/changed classes??
It appears that the 4.7 SDK cannot work with the new (default) R8 compressor.
You can get back to a working app by adding the following to the gradle.properties class:
android.enableR8=false
Are you using Mapbox SDK in your application? The issue might be related to pro guard rules. Refer the following Link to a similar issue
I have created new cross-platform Blank App(Native Portable), but the app was not running.
I got output message:
Android application is debugging.
The application could not be started. Ensure that the application has been installed to the target device and has a launchable activity (MainLauncher = true).
Additionally, check Build->Configuration Manager to ensure this project is set to Deploy for this configuration
I'm sure that MainLauncher is set True and this project is set to Deploy.
I've already installed the Android SDK platform for API Level 17,19 and 23.
Application setup:
Xamarin version:
Could you please give me any solution to resolve this problem?
Thanks!
I could not reproduce this problem. Usually minor problems in Xamarin can be solved by cleaning and rebuilding whole solution.