I uploaded my first Nativescript app to the apple app store and got a message that my build used SDK 11 and was ok, but future releases will be required to use SDK 12. I have been unable to find where you set the SDK the compiler uses. I have used a combination of command line to build at times, but usually the Sidekick app. Can someone help me know how to get my project to use SDK 12?
Related
I am receiving the error message below when trying to release a Xamarin Android app on the Play Developer Console
Upload failed
Your app currently targets API level 26 and must target
at least API level 28 to ensure that it is built on the latest APIs
optimised for security and performance. Change your app's target API
level to at least 28. Find out how.
I have the following settings in VS for Mac
Also, all of the Xamarin.Android libraries that I am using are v28.0.0.3.
It must be an issue with your Android support libraries or the version. Can you ensure the below and try to publish it with a new version?
Ensure the latest SDK (API level 28) is installed in your Android SDK Manager
Ensure you have the latest Android Support libraries and Build tools installed.
Set your Android Target version to API level 28 and Minimum Android version to something lesser than that.
Following points you should note:
When Google play talks about target Android version it is talking about the Target Framework in your Android Project Properties.
The error message that you are getting has nothing to do with what version of support libraries that you have. But when you target the latest version you might want to have the support libraries of the same version.
Adding all the SDK's that your Android app is going to support is recommended which means if you Min Android support version is 21 per se and you want to target the latest version then make sure that your Android SDK has all these sdks's so that there are no issues while parsing your APK in the desired version.
I wouldn't recommend that your min Android version is set to version 9 because of the fact 90% of the devices do not have this version of SDK which means none of them will be able to install or use your APP. Which if you ask me should never be the case. Supporting the widest possible audience is always the best call.
After making the above changes your app should work fine. Feel free to get back to me if you have any questions or queries...
I try to create a new Xamarin.Forms project for Android and Windows Phone, but I'm getting stucked by two errors.
First of all, I have the following error:
DEP3321: To deploy this application, your deployment target should be running Windows Universal Runtime version 10.0.16299.0 or higher. You currently are running version 10.0.14393.0. Please update your OS, or change your deployment target to a device with the appropriate version.
I've found the solution for this error, on some forums people said that setting the TargetMinVersionPlatform to the current running version of Windows Universal Runtime and setting the TargetVersionPlatform to the expected one should resolve the error. Yes it's true, but now I'm receiving another error:
NU1201 Project App3 is not compatible with uap10.0.14393 (UAP,Version=v10.0.14393) / win10-x86. Project App3 supports: netstandard1.6 (.NETStandard,Version=v1.6)
and after I did some research I found that this problem is resolved by doing backwards all the workarounds that I've did for resolving the first problem.
So, in conclusion I'm being stucked between this two errors. Can anyone help me?
Thank you!
As the .NET Standard document, netstandard 2.0 can be used on UWP version 10.0.16299. It can not be used on UWP version 14393, so you can not change your app target min version to 14393. Currently, Windows phone version is 15254 and you can not run the .net standard 2.0 on windows phone. So the solution would be like # magicandre1981 said on his thread Xamarin.Forms UWP project wont install on windows 10 mobile
Besides, you can also try to create your Xamarin app target version 14393 on the VS 2015 directly.
Since updating my Mac to XCode 8 (For iOS 10 support) Xamarin Studio is not including the Build # in archives. In the Archives window the build number (Code column) is empty, then when uploading the IPA to our Enterprise app store we get an error saying the Build # is invalid.
Has anyone else run into this issue since upgrading? I've tried restarting Xcode, Xamarin and the Mac itself with no luck.
Ended up being unrelated to my recent XCode update. Rather, we had previously pushed a version "0.2.1" which equates to "21" in our EMM solution (it ignores 0's). I'm not sure if the same can be said about the App store. So version 1.0.1 = 11, which is less than 21 thus the build # error. I'm not sure why Xamarin no longer shows the build # in the Archive screen but it ended up not being related to the problem we were having.
I recently updated Xamarin. Ever since that time, I have been unable to build my iOS application due to this error:
Your application is using the 'HealthKitUI' framework, which isn't
included in the iOS SDK you're using to build your app (this framework
was introduced in iOS 9.3, while you're building with the iOS 9.2
SDK.) This configuration is only supported with the legacy registrar
(pass --registrar:legacy as an additional mtouch argument in your
project's iOS Build option to select). Alternatively select a newer
SDK in your app's iOS Build options.
Has anyone else seen this? I haven't changed anything in my code.
Looks like you need to upgrade to Xcode 7.3. Could you perform that update and let us know?
iOS 9.3 requires Xcode 7.3 support, these were added in Xamarin.iOS 9.6.0.0: https://releases.xamarin.com/stable-release-ios-9-3-xcode-7-3-support/
Also, check out the following for information on iOS SDK releases against Xcode releases.
I have an app built in XCode 4.6 and I'm trying to install it onto an iPad with iOS 5.1.
In the target summary I have set the deployment target to 5.1 and in the build settings the base SDK is set to latest (6.1). From what I have read this should work but when I install the app via the IPA file and iTunes the app starts and then flashes off.
It runs fine if I build and install through Xcode.
Is there something I'm missing here? Am I incorrect in thinking it will work if the base SDK is iOS 6.1 but the deployment target is 5.1?
I did double check the profile stored against the release configuration and found it was incorrect. So Kevin was right. Thank you.
It had been my understanding up til now that a profile error would prevent installation altogether. I know better now.