xcode 9.2 Assest catalog issue - xcode

In one of my app I am facing this issue in Xcode 9.2. I have created my project in Xcode 8.3 and when I am running in Xcode 9.2 it shows me error like
Failed to find device type for System content for
IBCocoaTouchFramework-ElevenAndLater
scaleFactor=2x
Failure Reason: Could not find a suitable device type for the idiom
I am using Xcode 9.2 (Version 9.2 (9C40b)).I am not able to identify
problem.
It gives me error in assist catalog Any one have any idea ??

Hope this gets you well
Try to clear your derived data.
Try to completely restart your computer after downloading the new Simulator runtimes within Xcode for things to start working correctly again.
cheers :)

Related

Failed to start remote service on device problem in xcode

I create a flutter app and now I'm trying to run it through XCode on my real iPhone, but after the installation finishes, I face the following problem:
Also with I trying to run the application on my real phone, after clicking on the application icon, I face a white screen appears, and then the application closes directly.
Catalina 10.15.3
IOS 14.2
XCODE 11.7
Also I was make a trust to app in phone
Does anyone know the reason for this problem?
This problem maybe because of two reasons:
First: Xcode 11.7 doesn't have support files for iOS 14 you can download it from here https://github.com/filsv/iPhoneOSDeviceSupport
Second: I have this problem now and I couldn't fix it.. but I have iPhone with iOS 14.2 and iPad with iOS 14 so the problem was just on the iPhone but after I updated the iPad with iOS 14.2 it happened with it.. so the problem maybe because of the iOS 14.2 so we have to wait for the update or because of the Xcode 11 version and we have to download the Xcode 12 version..
I hope we can find a solution quickly...
make sure to have the latest system update on your target device and the latest Xcode version as well. The error should disappear.
Best,
Ralf
I have fixed the problem by using the above solution but it has happened again. So, I have followed these instructions and fixed again:
https://stackoverflow.com/a/61665031/6586109
A good first place to look is Window > Devices & Simulators in xCode, then find the details for your device. There may be error information here that helps you find the fault.
Restarting devices and installing updates seem to fix this problem for a lot of people.
For me, there was a red notice in the device window about connection to the device and it turned out to be the cable that was at fault.
This was an official Apple cable, just a few months old, and still works fine for charging and data transfer; and I've been using it with xCode without problems for a couple of months. It seems to be possible for Apple cables to develop some tiny physical fault that seemingly only xCode is sensitive to.
Using a different cable worked first time for me.
There seem to be a few variations on the exact error message with the same root causes varying depending on exactly what xCode was trying to do at the exact moment it failed: I'm on xCode 12 and for me it was:
Failed to start remote service on device
Failed to start remote service com.apple.installation_proxy on device

Xamarin.iOS crash on 6.1 simulator

i recently received my Macbook and wanted to start developing iOS apps with it.
I Created a default Master-Detail App using the Templates in Xamarin.Studio and everything worked.
Now today i wanted to actually do something in the app, but didn't change a single line of code, still the app doesn't show up anymore in the simulator as long as i want it to use the 6.1 sdk for ios. if i use any other (6.0 etc) it works fine.
I already tried clearing my Cache in /Users/MYNAME/Library/Xamarin/ but this didn't change anything.
What would you suggest me to do now? can i simply reinstall the 6.1 sdk?if so, how would i do this?
Thanks for your help
I had a similar problem where the environment hang when I was trying to debug in the simulator (just showing the spinning ball). I found out that it only occured if I had my phone connected to the computer. Perhaps not valid in your case, but it might be a lead in your problem solving.
I'm using the latest version of everything. :)
From within Xamarin Studio (or MonoDevelop):
Project -> Your.Application.Name Options
Build -> iOS Build (iPhone Build in MonoDevelop)
SDK version: -> 6.1 (it's probably still on 6.0)
This fixed it for me. Also, it wouldn't hurt to make sure the target build in info.plist is set to 6.1.
Delete this folder:
/Users/[username]/Library/Application Support/iPhone Simulator/6.1
And if your Library folder is hidden:
sudo chflags nohidden ~/Library/
I have experienced this problem several times again and my previous answer doesn't solve it. Ya know what does? Rebooting the computer. Works every time. shrug
You need to fill the Application name, Identifier, Version # in the project setting.
I had the same problem and got it solved that way.

Xcode no codesign_wrapper

Im using Xcode 4.4 on Mountain Lion OS X 10.8, to archive an iOS app however I keep receiving this error:
(null): There is no codesign_wrapper executable. Please reinstall the Xcode developer tools. (-19058)
Has anyone come across this problem or know how to solve it?
Thanks, Sami.
Do you need to install the command line tools via xcode?
they are located in the Preferences window's Downloads section and the Components tab.
In case anyone else comes across this as well...I was having trouble with this for hours while trying to submit the application with the Application Loader. Perhaps its a slightly different issue, since your getting this error while trying Archive, but for what its worthere this is/was my situation
. Using the "latest" Xcode 5.0.1 (past what I saw other threads saying - using 4.0.x), eventually installing Xcode 5.1 when released with the same error/issue. After upgrading, I believe I was still receiving the issue because I was still using the same (2.9) Application Loader from the first (5.0.1) Xcode. When I explicitly opened the new (2.9.1) Application Loader from (5.1) Xcode via Xcode --> Open Developer Tool --> Application Loader, the submittion process went futher. However failed for me for a different issue.
So it goes.

Xcode Crash while "build and archive"

i have snow leopard 10.6.3 installed via iAtkos..everything runs good even XCode as well.I can successfully build iPhone apps run them on the simulator and the device but when i use the "build and archive" option( for adhoc distribution or itunes connect ) XCode simply crashes..does anybody have a solution for this?
thanks in advance
btw XCode version 3.2.3(tried 3.2.3 as well same result,also in safe mode)
Mac OS X version 10.6.3
I had the exact same problem, and it turned out it was caused by a variable of wrong type in info.plist. My short bundle version was created as int instead of string.
I was getting the warnings about it, but it didn't seem relevant since the crash happened only when archiving, and normal building worked fine, the app ran fine. I suggest you check your benign looking warnings, one of them could fix the issue.
You might try 3.2.4 (available now).

XCode 3.2.4 iOS 4.1 (Final) and CoreData Crashes in Simulator

I've got 2 applications using Core Data with a sqlite persistent store. I've got a data loader routine that I run to populate the CoreData DB from csv files. During development, when my data changes I run the routine from the simulator to generate new databases and copy the new one into the project.
This has been working quite well for XCode 3.2.3 and iOS 4.0. It even works in the XCode 4 Preview 2 and 3. I just installed the final version of XCode 3.2.4 and iOS 4.1. Now my db loader fails. It gives me no message, no warning, no nothing. It just dumps out to the spring board and XCode gives me the "Debugging Terminated" message. It will fail at different times during the load so I'm pretty sure it's not a data issue. I'm not doing any threading. I assume the issue has to do with either Core Data or sqlite, since that's when the crash occurs, but with no info reported I can't tell for sure.
I uninstalled everything. Xcode 3.2.4, Xcode 4 preview (assuming it was an issue caused by XCode 4) and reinstalled XCode 3.2.3/iOS 4.0. Things returned to normal. After getting some work done I attempted to upgrade to 3.2.4/iOS 4.1 again. I uninstalled 3.2.3/iOS 4.0, rebooted. Installed 3.2.4/iOS 4.1, rebooted and tried again. No luck. Same hard crash. Same lack of messaging as to the cause.
I have determined that this only happens with the Simulator with XCode 3.2.4, the device is fine as is XCode 4 and 3.2.3. I've tried playing with the target OS selection (3.0,3.1,4.0,4.1). I've tired adjusting the Compiler from GCC 4.0, GCC 4.2,LLVM GCC 4.2, LLVM 1.5. I've tried setting the Base SDK to iOS Simulator 4.1. Interestingly enough it will work in the iPad simulator when using the 3.2 SDK. So I've at least go that as a work around.
I guess there is one of 3 issues:
An issue with my code that has been uncovered by 3.2.4.
Bug in 3.2.4.
A configuration issue that I've missed.
If anybody has any troubleshooting ideas or answers I'd love to hear them. I've been doing iOS full time since V 2.1 and I am seriously stumped.
Thanks in advance,
I figured out my issue. It looks like the CoreData/Sqlite connection was a total red herring. Following a tip I read on SO, I used OSX's Console application and got a critical message "Failed to launch in time" that was not being displayed in XCode's debugger console.
It looks like the process was being killed due to what is essentially a timeout error. The iPhone will kill an application that takes too long to complete "didFinishLaunching." That's where I was kicking the data load routine off from. The new version of XCode must have adjusted it's timeout values.
So my takeaway is give OSX's console a shot if XCode isn't telling you everything and watch out for those red herrings.
When I upgraded I ran into troubles in the simulator when saving the managedObjectContext. I finally deleted my sqlite CoreData store file and have not run into similar problems. Try deleting your data file (well save a copy of it before deleting to see what is different).

Resources