I have an app that uses sqlcipher encryption, and with the latest release of Xcode I haven't been able to to run on simulator, I always get the following error.
Building for iOS Simulator, but the linked library 'libsqlcipher.a' was built for iOS.
I have researched that this error may be connected with Apple wishing us that move from .framework to .xcframework.
The open source of this library doesn't offer a .xcframwork. And I'm not sure I can build it locally.
I would like to ask if there is any workaround that can be done without having to purchase sqlcipher.
Related
I am facing problems while submitting the react native ios app on App store. It works well. There is no problem in archiving also. But after archiving , When I try to distribute
the app I get an error "Found an unexpected Mach-O header code: 0x72613c21".
Xcode version: 11.1
I ran into the same problem although I think it was my own fault. I was upgrading an App for Admob 8 and the compatible Firebase version and I think while cleaning out the previous versions I deleted all the entries in General -> Frameworks, Libraries, and Embedded Content without realising that I also had GameKit and StoreKit frameworks in there. Whilst this carelessness had no effect on building and running for simulators and devices I got the Mach-O error when I tried to distribute the app to the store. Just dragging the frameworks back in fixed the problem for me.
i'm trying to create my first app using Phone Gap, so i manage to Build a "generic" app, after installing node.js and phonegap.
So i'm trying to run the following command on the terminal:
phonegap build ios
And it always get stucked on [phonegap] Detecting iOS SDk Environment.
I have, xCode 5, and i do have all the profiles needed to develop, and distribute for iOS, in fact i couple of hours ago, i just send my first app to Itunes Connect, so i think my environment, is fine.
Any ideas? Thanks for the attention!
So, instead of using the command phonegap build ios, I tried phonegap run ios. The program runs, and also a folder was created with the xCode files.
I still dont know what was wrong, but it worked for me.
I'm working on a iOS project in Xcode 4.5 and I have a workspace with some old libraries that I needed to link as dependancies to my project. I had to go through quite some difficulties before getting it to build and now it finally builds for my device, but not for the simulator. The problem is, I get a bunch of errors like the following (all related to UIKit framework):
- error: 'UIResponder' is unavailable: not available on Mac OS X
and then it just says too many errors emitted, stopping now.
It looks like it's trying to build the project for Mac OS X rather than for iOS, and I have no idea why.
I'm quite new to Xcode 4.5 development and it might just be that I missed something really easy, but I can't seem to find the solution anywhere!
How can I convince Xcode that the iPhone simulator is not Mac OS X?
Make sure that the deployment target is the latest (6.1), the base SDK is iOS 6.1 and targeted device family is iPhone. All these options can be found under the build settings tab for the PROJECT.
I have been testing my app on my iPhone 4S and my wife's iPhone 3GS. I would also like to test it on the older iPhone 3G running iOS 4.2.1 (the highest version it will support).
When I connect the 3G to my Mac and attempt to provision it, I get two error messages:
Could Not Support Development
and
Xcode cannot find the software image to install this version
I am using the latest version of xCode (v. 4.4.1).
Is there some place to find the missing 'software image' in order to test my app on the 3G and older iOS devices?
If not, how does one know what devices the app will work with?
I do note that the newer iPhones that run iOS5 and above also support Automatic Reference Counting (ARC). I have checked the ARC button whenever I created a new project. Does one have to abandon ARC if one wants their app to work on an older pre iOS5-capable device?
...Dale
Is there some place to find the missing 'software image'?
I believe you can download it through iTunes by clicking restore in the device's summary page and then searching for the *.ipsw file. iTunes might even share the image once it is downloaded automatically.
Does one have to abandon ARC if one wants their app to work on an
older pre iOS5-capable device?
Not in entirety. iOS 4.2 supports the vast majority of ARC, But it does not support weak references.
Also, there are a few hoops you must jump through to target. I have an answer here that outlines them (with screenshots).
I know for a fact that Xcode 4.4.1 can use an iOS 4.2.1 device as a target, since I can test on a second generation iPod touch running 4.2.1.
Finally, If you are not able to obtain a software image, you could try adding your device by UDID directly on the provisioning portal through developer.apple.com.(The old fashioned way)
I don't have the Apple 79€/year account. In iOS 5.0 and Xcode 4.2.1 I changed SDKSettings.plist ecc... And it works. In iOS 5.1.1 and Xcode 4.3.2 no, I already changed settings ecc but don't work, the app installs on device but crash on launch... How can I run my app on device without crashes? Thanks, and sorry for my english.
I have had this issue before on a jailbroken device. You have a few solutions depending on the exact issue. First you can install app sync in order to allow unsigned code to work on your device if you are not using a valid code signing identity. The second option is to actually get a valid code signing identity along with the provision profile so you can run the application correctly. This involves paying for the developer program so this may not be the best option.
Last is a very common issue with jailbroken devices. Which is that you will receive an error such as "failed to get the task for process xxxxx". This tends to happen a lot with jailbroken devices. This is because Xcode notices you are not using a provision profile that is required to report error logs. All you have to do is launch the application again on the device and everything should work.
This is just Xcode not being able to fully launch your application because of the missing provision profile so it results in a crash. If none of these solutions solve your problem please post a more detailed explanation of the issue you are having.