Xamarin forms ios sdk versions mismatch issue - xamarin.forms

I recently updated my Visual studio for windows and mac. I also updated the Xcode to 10.2. The visual studio 2017 for windows version is 15.9.11 and the xamarin ios sdk version is 12.4.0.64. My visual studio version of mac 2019 community is 8.0.2 and xamarin ios version is 12.8.0. Why I did these updates is I got a mono version mismatch issue when compiling ios app. After these updates the mono version conflict resolved but now it shows xamarin ios version mismatch error. How can I solve this? I am trying to solve these for some days. Any help is appreciated.

Related

Android and Java win 10 compatibility

I would like to learn android using android studio. But I do not know which java sdk, android sdk and android studio are win 10 compatible? Any help will be appreciated. Thanks.
Start from here: https://developer.android.com/studio/intro
You don't have to worry about compatibility as Windows 10 is the latest and latest version of Android Studio is compatible with it.
The latest version of Android Studio is 3.5 at the time of writing this.

Visual Studio 2019 and iOS: native linking failed

I have my Xamarin solution in Visual Studio 2019 for Windows. I can build the solution for UWP and Android but I receive a lot of errors when I try to compile the project for iOS. Here the list of errors:
Generally, the errors are similar to the following:
Native linking failed, undefined symbol: _kFIRAppDiagnosticsNotification. Please verify that all the necessary frameworks have been referenced and native libraries are properly linked in.
On my Mac, I have the latest updates for the OS and XCode. Visual Studio 2019 for Mac is installed.
I checked the iOS Build and I changed the Supported Architectures with:
If I use the default value ARM64, Visual Studio compiles the solution but at the end of the copying on the device, there is an error:
APIInternalError: Failed to unhide archs in executable file:///private/var/installd/Library/Caches/com.apple.mobile.installd.staging/temp.ReCcst/extracted/WordBankEasy.iOS.app/WordBankEasy.iOS
Update
I noticed the problem is coming from Xamarin.Firebase.iOS.AdMob version 7.38.0: if I remove it, I can deploy my app on a iOS device.
How can I fix this issue?

apk is installed but not working on android 6.0 version only xamarin forms

I am developing my android app using xamarin forms. The Released apk install on even Android 5.1.1 and above Android 6.0.1 version is working fine.
But When i installed on Android 6.0, it is installed. But when i open the app, this shows 'The App is unfortunately Closed' error.
Can anyone help me to resolve this issue.

SDK Mismatch Errors UNSUPPORTED_SDK_VERSION_ERROR on android from OSX development

using android studio 1.5.1
JRE 1.6.0
with the newest Android band sdk microsoft-band-1.3.20105.2.jar
developing on osx 10.11.2
targeting a galaxy not SDK version 22 (min version stated as 17)
trying to run the sample code
BandInfo[] devices = BandClientManager.getInstance().getPairedBands();
throws
UNSUPPORTED_SDK_VERSION_ERROR
What am I doing wrong?
Most likely the error message is "The version of Microsoft Health installed does not support this application. Please update to the latest version of Microsoft Health.".
So, all you should have to do is update the version of Microsoft Health you have installed on your phone.
Each new version of the Microsoft Band SDK appears to only work with the latest version of Microsoft Health, as it is that application that holds on to the Band's Bluetooth connection.

Android Emulator in Aptana Studio3

Can I run the Android SDK emulators for Android website testing in Aptana Studio 3?
Do I need to install the Eclipse plugin?
I have installed Android SDK, and use Aptana Studio 3, but I am not sure if they will work together.
Thanks in advance
Ant
I don't see a major conflict by installing both plugins into Eclipse.
Aptana Studio's 'younger brother', Titanium Studio, can run both, so no real reason why the studio wouldn't run both as well.
In any case, if you stumble into issues like that, you can open a ticket at http://jira.appcelerator.org/secure/CreateIssue!default.jspa

Resources