When I am trying to release iOS App from Visual Studio. I keep getting this failure
Severity Code Description Project File Line Suppression State
Error /Users/uc/Library/Caches/Xamarin/mtbs/builds/NexaLabIOSApp/a7eb932ce124a373359a36ab8d9e7fee/bin/iPhone/Release/NexaLabIOSApp.app/Frameworks/IQKeyboardManager.framework/IQKeyboardManager: errSecInternalComponent NexaLab IOS App
Related
I have a Xamarin.Forms app, but this concerns Xamarin.iOS only.
I want to run the app on an iOS emulator, but I get an error which I cannot find on the internet. This prevents me from testing my app on iOS. This happens ever since I updated Visual Studio 2019 to version 16.9.0.
The main error is "ibtool exited with code 72", but this causes a list of errors:
Does someone know how to fix this?
I bought the source code of an app that was written with a flutter framework After implementing it on Android Studio I encountered this problem That the Android Studios run button has been disabled and I can't run the project.
You can see more details in the photo below.
I was able to debug my Xamarin cross-platform app on iOS as well as Android using Visual Studio 2015 on Windows. Recently, I installed Xamarin updates on Windows as well as Mac. After the upgrade, I am no longer able to debug portable library from iOS app. Breakpoint hits MainActivity.cs but later it doesn't stop at other breakpoints in portable library.
However, if I open the same project in Xamarin Studio on Mac, I can debug iOS and Android app.
Anybody has any idea about the possible solution for the issue?
Windows:
Visual Studio 2015
Xamarin 4.5.0.486
Xamarin.Android 7.3.1.2
Xamarin.iOS 10.10.0.37
Mac:
Xamarin Studio Enterprise 6.3
Xamarin.Mac 3.4.0.36
Xamarin.Android 7.3.1.2
Xamarin.iOS 10.10.0.36
XCode 8.3.3
iOS 10.3
I have a mac setup as a Xamarin build agent for Visual Studio and Visual Studio Team Services (VSTS). On Friday, Xcode updated itself to 8.0 with the iOS 10 SDK. This, of course broke everything. I managed to get Visual Studio to reconnect after upgrading both Xamarin iOS on the mac and Xamarin for Visual Studio.
Now, my only issue that is that the VSTS agent fails to build. This agent runs on the same machine as the Visual Studio agent that works (e.g. I can build in Visual Studio and it builds on the mac and gives me an ipa). I haven't changed any build settings since the upgrade.
Here is where it fails, in the Xamarin Activation build step:
Yes, I double and triple checked that the XamarinPassword variable is correct. In fact, if I enter the wrong password, it will fail with an invalid login error.
Here is the error:
******************************************************************************
Starting: Activate Xamarin license
******************************************************************************
warning MT0061: No Xcode.app specified (using --sdkroot), using the system Xcode as reported by 'xcode-select --print-path': /Applications/Xcode.app/Contents/Developer
error MT0052: No command specified.
/Library/Frameworks/Xamarin.iOS.framework/Versions/Current/bin/mtouch --datafile
Xamarin.iOS 10.0.0 using framework: /Applications/Xcode.app/Contents/Developer/Platforms/iPhoneSimulator.platform/Developer/SDKs/iPhoneSimulator0.0.sdk
Failed to activate Xamarin license. {"code":1,"message":"An internal error occurred. Please email us at contact#xamarin.com and make sure to include the address associated with your Xamarin account ."}
Return code: 1
Is the VSTS agent ready for iOS 10? Should I downgrade everything back to before Friday and before the Xcode 8.0 update? Am I missing something new in the configuration?
The solution is that you can remove Xamarin license task, because it is no longer needed to build Xamarin app. (refer to this article)
I have installed Xamarin 2.0 and i can now starte the iphone simulator from visual studio. I have added another Iphone resource prefix to my project Resources;images
When i run the app from Visual studio the resources in the images folder is not included in the app. If i run it from Xamarin studio on the mac, it all works fine.
Any suggestions on how to fix this ?
This appears to be a bug in the Xamarin.iOS addin for VS. I filed it.