I've built my solution in MonoDevelop, then created an Xcode project in Unity with the following settings
I have then successfully deployed the app to the iPhone, stopped the Xcode project, reopened the app on the iPhone and then attached the MonoDevelop debugger
The problem is that when I set breakpoints, they show as unreachable and don't get hit at all.
Can anyone point me in the right direction with this? The stress of it is killing me..
Thanks
Spec:
Macbook Air Early 2015 - El Capitan 10.11.6
iPod Touch (MGG72BT/A) - iOS 9.3.1
MonoDevelop 5.9.6
Unity 5.3.4f1
I had the issue on Linux and I noticed that it started happening after I manually built the project in MonoDevelop, which gave me a bunch of build errors that were due to the fact that the version of .NET unity was targeting was 3.5 but the one came with MD was 4.5. So after I changed the target FW to 4.5 the build errors (in MD) cleared BUT the breakpoints stopped working.
What I did was I restarted both MD and Unity, Cleaned project in MD BUT DID NOT BUILD THEM IN MD. Just saved and switched to Unity which uses its own build. After that I switched back to MD and attached to Unity process WITHOUT BUILDING.
After this the breakpoints started working again. Conclusion - do not build the project in MD, just use it for editing scripts only and let Unity do the building.
Related
environment:
Develop OS:macOS Catalina 10.15.5
Xcode:11.5
Device OS: iPhone 7 Plus (iOS 13.5.1)
Unity : 2019.3.9f
I built the iOS app with Unity.
When I play on the Running on device on Xcode, the app works normally.
However, when I turn off the Xcode and turn on the built app, the black screen comes out and stops.
If I run it on the simulator to check the log, the following log occurs.
Could not find and/or execute program specified by service: 86: Bad CPU type in executable: /Users/develop/Library/Developer/CoreSimulator/Devices/31985C61-CACF-40D6-8A48-A2BA2BAF0DDD/data/Containers/Bundle/Application/EC20344C-A067-4379-A9EA-CE0E42F3C106/make.app/make
Service setup event to handle failure and will not launch until it fires.
Service exited with abnormal code: 78
But when I play on the Running on device on Xcode, I can't understand the app running normally.
I tried the Unity version 2018 to figure out the problem, but it works well. However, when I upgraded the Unity version to 2019, the above problem occurs.
I want to know the causes and solutions of these problems in Unity 2019.
On Xcode
Go to Unity-iPhone - Build Phases - Link Binary with Libraries build section
Add UnityFramework.framework
This happens on Unity 2019/2020
I am trying out Xamarin on the Mac. I have an oldish Mac that DID have Xcode 10.1 on it.
I tried to build the iOS app and got the following error:
Severity Code Description Project File Line Suppression State
Error The Xcode version installed on the Mac (10.1) is not compatible with this version of Visual Studio. This may cause unexpected warnings or errors when building and deploying iOS projects. Please install Xcode '11.3' or visit the documentation to learn more. 0
I upgraded the Mac to Caitlin and upgraded Xcode to 11.3.
I can connect to the Mac and actually can run the iPhone simulator with the app, however, if I run the build, I STILL get the same error, like its not figured out how to update itself?
I have done the 'forget this Mac' and even renamed it on the network in case there was some legacy in a file somewhere.
I have dumped the solution and created a new one from the templates and still get the same error ... hair being torn out...
It might be one of those things that just goes away after a while I don't know. Any ideas?
Thanks.
EDIT * I realised that I wasnt clear. I am running VS2019 on a PC connecting to my Mac.
I'm getting these errors, building for any iOS simulator:
C:\Program Files (x86)\Microsoft Visual Studio\2019\Professional\MSBuild\Xamarin\iOS\Xamarin.iOS.Common.targets(473,3): error MSB3231: Unable to remove directory "obj\iPhoneSimulator\Debug\". The directory is not empty
OR
SeverityCodeDescriptionProjectFileLineSuppression StateSuppression State Error Unable to remove directory "UserControls". Access to the path 'D:\Projects\Solutions\mycompany\iOS\obj\iPhoneSimulator\Debug\UserControls' is denied.mycompany.iOS
OR both together...
I'm using VS 2019 version 16.3.7 on Windows 10 machine and Xcode 11.2.1 on Mac Mini, OSX 10.14.6 and it does not matter which iOS simulator targeted, all version 13.2.2. Developing a Xamarin Forms application.
If I switch to target one of my hard devices, I get multiple errors like this:
error : Access to the path 'D:\Projects\Solutions\mycompany\iOS\obj\iPhone\Debug\Popups\TemplatePicker.xaml.g.cs' is denied.
I can work around this by quitting VS, removing read-only flag on the obj folder and all it contents, run VS as admin, THEN it builds and pushes to the device.
Switching back to target a simulator, I get the first error again.
Deleting Bin and Obj folders does not help either.
Side note - this was working until Windows rebooted itself on my dev machine, closing VS and forcing recovery of some files. Android version works just fine in simulator and hard device, no issues.
Wondering if I upgrade VS to version 16.4.5 and Xcode to 11.3.1, this might be resolved. Any ideas?
Are these version compatible with the latest VS-Xcode connector? (I've seen issues with version incompatibility) .
Any ideas? Resolutions?
Thank you
OK, here's what I've found...
The connection and link to XCode from VS on the PC causes a lock or some sort when targeting any iOS simulor. This is intermittent but once the locks are imposed, one needs to
close VS
quit the Simulator on the Mac.
delete the Obj and Bin folders in the solution
Re-open VS, open the project, let it sync with the Mac.
Restart Simulator on the mac
Rebuild. This could take a couple iterations too.
If that does not clear the problem, shut down both machines, remember to delete Obj and Bin folders.
Frustrating, slow, but it works for me for now.
Scenario:
I have updated to Qt 5.9.6 and I have Xcode 10.0 running on High Sierra.
I have a Qt App that builds for OSX and iOS. And it builds and runs all well with Qt 5.9.4.
Now, I want to update to 5.9.6 for a reason. When I try to build for iOS using Qt 5.9.6, I get the following error
Project ERROR: This mkspec requires Xcode 4.3 or later
Question:
Is there a way to get around this issue?
Note that the OSX build using Qt 5.9.6 just works fine. I have QMAKE_IOS_DEPLOYMENT_TARGET set to 10.0 for iOS case
PS:
I also deleted the .qmake.stash and the .pro.user file from the root directory and restarted QtCreator to try build from a a fresh start. But still get the same issue!
This is bug in Qt, use Qt 5.9.7 where this bug is fixed.
I am getting the following error when trying to run Visual Studio/Xamarin built application on the IOS Simulator.
Launch failed. The app 'App2' could not be launched on 'iPhone 7 Plus iOS 10.1'. Please check the logs for more details.
"App2" was created using the Tab Template, and NO code changes after rolling the application.
Windows environment: Windows 10 w/Visual Studio 2015 update 2
Mac environment: IMac Sierra fully patched. XCode 8.1 (what ever is most up to date).
I have connected the mac remote and pc. I can launch the iPhone simulator on the mac from Visual studio on the PC.
I get the error when trying to run "App2". It compiles fine, just won't run on the simulator.
I've searched here, and similar results speak of VS Crashing. Mine doesn't crash, just presents the error. NOTE: There's nothing in any log I can find with details by the way.
Ideas? Thanks!
EDIT: Just loaded up Parallels on the IMac and ran Win 10/VStudio. I get the same error. Again, xamarin remote agent connected and I can start the simulator from the PC, i just can't deploy to it.
After all the research and help from those here it comes down to a bug with the current version of Xamarin. Options are to wait until a new stable build is on the Xamarin site or get builds off of GIT. I'm choosing to wait, as I've not had great luck working with interim builds.
Xamarin that downloads with the new VS 2017 fixes this bug.