After upgrading to XCode 8 I am no longer able to run or debug my application using AppCode. I am running version of 2.16.2.3 of AppCode. After attempting Run|Run from AppCode's menu I get the following error in the messages tool window.
Error:Build failed in 2s 432ms
Note:Code signing is required for product type 'Application' in SDK 'iOS 10.0'
XCode is able to build, run and debug the application with no problem. I have code signing identity set to Automatic/IOS Developer for all configurations of my target. I've tried Invalidate Caches/Restart from AppCode but no luck.
Anyone have any ideas?
Thanks
JetBrains support figured it out. Some kind of bogus data in project.xcworkspace directory. Cleaned that out and everything is fine now. See https://youtrack.jetbrains.com/issue/OC-14584
Can you try to update your IDE? I had a similar problem few weeks ago, but than after some version it disappeared.
Now, my AppCode version: AppCode 2016.3 EAP
Build #OC-163.7743.19, built on November 9, 2016
Related
I am trying to run the initial example apps generated by the Kotlin Multi Platform Mobile plugin in Android Studio. I followed these steps for my environment setup. The Android Simulator runs correctly, but the iPhone Simulator does not. The Run Configuration has the following error:
Error: Selected scheme "iosApp" does not support "iphonesimulator"
When I run the configuration (ignoring the error), the iPhone simulator does open and appears to load iOS, but it never loads the "Hello, iOS" application that is in Android Studio.
What would cause this?
Version Information:
macOS 12.2.1
Android Studio 2021.1.1 Patch 2
Xcode 13.3
I fixed it with the following method.
Please close the Android Studio.
Go to ~/Library/LaunchAgents/ folder and delete com.jetbrains.AppCode.BridgeService.plist there.
Launch Android Studio with the KMM plugin again. It should work now.
From my tests, it seems that there may be multiple reasons for which we receive this error:
the root folder of the ios project has a different name than the .xcodeproject file. Sometimes it works even if they are different and maybe it matters if we change this name after the frameworks was already connected to the iOS project.
"Other linker flags" were manually copied and they were not copied using the copy button from the Connect the framework to your iOS project. This results to wrong data like:
"$(inherited)",
"-framework",
"shared\n",
instead of
"$(inherited)",
"-framework",
shared,
I managed to fix this by going into Edit Configurations on Android Studio and choosing the location of my XCode project file again. I believe this is an error of the KMM plugin in Android Studio and has yet to be fixed.
Updating Android Studio and KMM plugin worked for me.
I have a Xamarin iOS and Android project with a dotnet standard 2.0 library that is being shared between the two operating systems. When trying to run my iOS project, the project build fine and doesn't give any errors but Rider cannot seem to deploy it to a simulator.
I will give the following error:
I thought it could be the problem what is described here, but that did not help. When running the project in VS on MacOs, the iOS project also build and runs on a simulator.
Failed to load Xamarin Forms project with .NET Standard 2.0 Lib in Rider
Can anyone help me trying to fix this, please?
You are not the only one with this problem, the problem is already reported multiple time in Riders issue tracker:
https://youtrack.jetbrains.com/issue/RIDER-15544
https://youtrack.jetbrains.com/issue/RIDER-15514
https://youtrack.jetbrains.com/issue/RIDER-15419
According to the last issue, it's fixed in Rider 2018.2, which will probably be released pretty soon.
I ported my Xamarin Forms project from windows to Mac and I am trying to run it on a connected device which is added in the provisioning profile (provisioning profile and identity is setup accordingly in IOS Bundle Signing settings).
Whenever I try to run the App using Debug|iPhone > my Iphone:
It starts simulator runs on that instead of the device :
After stopping the build if I go back to Bundle Signing settings its changed back to simulator automatically:
I am using following setup:
Visual Studio 2017 Community on Mac 7.2 preview build 540.
XCode 8.3.3
Can anyone please help me with proper configuration to run the app on IPhone?
Many Thanks in advance :)
After hours of messing around I finally found the problem and solution.
In solution settings, iOS project (Debug-iPhone) configuration was mapped to (Debug|Simulator).
Simply changed it to Debug|iPhone and Its working fine now.
When I build my project in debug mode it builds forever. However there is no problem building in release mode.
This problem first occurred when I updated visual studio for mac to the newest version:
Preview 6 (7.0 build 2740).
This is what my debug settings look like:
Any ideas are much appreciated.
Check for xamarin.forms updates in both in the ios and xamarin project. It could be that theese are not updated even though the solution is updated.
Xamarin.forms package under the iOS project might have an older version
I cannot really help you because I don't know what type of project you tried to run or which OS X you are working with.
If such an Error occurs, always check your code or try restarting your mac.
Tip: "Visual Studio for Mac Preview" is still in its Alpha. Use the Stable Update channel to avoid errors like this.
I just upgraded to XCode 3.2.5 and iOS SDK 4.2, and I upgraded my device to 4.2.1. Now I can only deploy a release version of my app. How do I deploy a debug version of my app? Do I need to install debug symbols on the device? If so how?
Perhaps this can solve your problem, at least it worked for me:
Change the build settings for base
sdk to latest iOS version
Change the active configuration to
Release
Choose Device in the same menu as
configuration
Switch back to Debug configuration
Choose Device in the same menu again
/Jakob
Go to the developer.apple.com site, sign in to the iOS member site, on the home tab is the Launch Assistant that will help you install your app to your device.
Two methods for running (Release vs. Debug Modes):
A) Run in Profiling Mode (it has Release Build set by default. Note: the NDEBUG macro is NOT set!)
B) Change the Run [appname] part of your build Scheme to Release mode temporarily, then back to the Debug default afterwards.
As for the device deployment part, I have not encountered this problem.
if you use an old iPod device, you should support armv6 version.
set "Architectures" , add "armv6" in both Debug and Release mode.