Upon attempting to "Distribute App" archive in xCode, I get this error:
WARNING ITMS-90863: "Apple silicon Macs support issue. The app has LSApplicationLaunchProhibited set to true. This is not supported on Mac."
I have iPhone and iPad checked, but not MacOS. It is my understanding that stand-alone stickerpacks are not supported on Big Sur yet (nor has there been a hint that this will ever happen).
These projects were made using the StickerPack template in Xcode - not as an iMessage application - so there is zero coding involved on my end. I set the deployment target. I added the accessibility info - but that is it. I have no code on my end to toggle or fiddle with.
This is a VERY new error which surfaced as of Tuesday. I believe this is on Apple's end - some sort of update on their servers, because I had already successfully uploaded a stickerpack to the AppStore through AppConnect w/ the same version of Xcode a day before.
I already had 5 sticker packs published in the App Store for the past 3 years. I published updates to 2 of them literally just days ago. Then they had the Apple Event on Nov. 10 about Silicate macs and literally the next evening I got this error when trying to update another stickerpack.
I learned from previous errors before this that you need to make your product deployment target as 10.x because anything higher will give you a completely different error about 32 bit and 64 bit architecture. I dealt with that crap for over a week before I figured it out. That's what happens when you don't touch xCode for 2 years. Oops!
So after the error I cited showed up;
I tried creating a brand new version of the sticker pack from scratch that I was trying to update - since all I had to do was drag in my assets and re-type in all the accessibility tags for the visually impaired. Still no go.
So then, I updated to Big Sur - installation successful. Still no joy.
Then I updated Xcode after Big Sur. Successful updating, but still no joy.
I created a new archive w/ a different build number. Validated it successfully - but it failed AGAIN with the error I cited above. I've searched the Internet for an answer or a clue w/o success, but I think this is so new, a lot of people haven't figured this out yet. I'm waving my white flag now.
see the answer I posted to ITMS-90747: Basic sticker pack with no code, yet App Store Connect thinks there's 32bit code in there
(Apparently I'm not allowed to share the same answer to multiple posts about the same issue. Everyone is looking for this solution and I want it to be known!)
In short: You can opt out of the Apple Silicon Mac on the connect hub website, under availability and pricing
Related
I have a question regarding the title above. I try surfing the internet for almost 2 weeks, but my issues were not solved.
I have an iPhone (iOS 15) and MacBook (macOS 13.6.1), want use XCode 13 to test the app. I got instructions from the Leapwork guy, to list how to do it. My colleague wants to test an app on iPhone, and she asks me to setup it up for her.
But I am facing a few errors which I don't know what are and how to solve because this is my first time playing it.
Here link to the document I manage success following the step from 1 to 8. I’m afraid to step 9 I did something wrong because it asked me to change a few things may I miss out.
iOS Instruction
The error that I have on XCode is
Building for iOS, but the linked and embedded framework 'RoutingHTTPServer.framework' was build for iOS + iOS Simulator
'assign' property of object type may become a dangling reference; consider using 'unsafe_unretained'
Double-quoted include "HTTPConnection.h" in framework header, expected angle-bracketed instead.
Could not build module 'RoutingHTTPServer'
I'm running Appium but not sure need to configure it or not.
I hope anyone knows about this or has been through a similar situation, please help and guide me on the correct path. I think I already lost. :(
Thanks.
Installed with testflight the application does appear in the list of target applications to share an image with. When I select my application icon in the list I do get a normal Post dialog. After pressing "Post" in the dialog the application does open but nothing else happens.
When the same version of application is installed with xcode the shared file is delivered and the application displays the shared image.
I am not even sure how to debug such an issue as the application installed by testflight does not appear in the list of installed applications in xcode Devices window. Nothing that I can find in device logs either.
Please suggest any approach to troubleshooting the issue.
Update: I found a way to get much more detailed logs from device than the one provided by xcode's "Devices" window: deviceconsole utility. This gives at least some information to approach troubleshooting.
Update 1: It turns out that the application installed through ad hoc ipa file exported from the same archive that was submitted to testflight shows the same problem. This allows much quicker testing turn around.
This answer indicates that the problem can be caused by "Deployment Target" of extension set above the ios version of test device. I did try different combination of this setting in the application and extension, nothing helped thus far.
Update 2: I created code-level support request with apple for this issue and provided full source of the application to them. After few months of apathetic communications they concluded that the problem is due to a bug and suggested to create report Apple Bug Reporter. I did that and after another few months of more apathetic communications the issue was promptly closed on the basis that the application does not crash. Frustrating, but I still need to resolve the problem, now looks like without help from vendor.
If the deployment target is higher than the version number of the actual phone, your code cannot run. So the only choice is reducing the deployment target of the extension to be the same as the app.
I’d check if you have somehow set different deployment targets for debug and release.
This is an app I'm helping out with remotely. I have some issues right after cloning repo..
Assets folder is marked as modified. git status results: modified: AppName/Resources/Images.xcassets/AppIcon.appiconset/Contents.json. One of many compile warnings says "A 1024x1024 app store icon is required for iOS apps". Is new 1024x1024 asset placeholder the modification that was made?
Many warnings:
The app is running well in App Store and has support for iPhoneX, so if I clone, shouldn't all this stuff be sorted out already? I still see layout issues when I run in simulator on any device size that were apparently fixed for iphoneX compatibility. When I was running Xcode 8.3 I didn't have these issues.
I need to add a feature, push and make build available on TestFlight, but I'm worried about pushing with all these compile errors & bet it wont even archive with missing 1024x1024 asset.
Question:
Should I just go back to previous version of Xcode rather than sticking with 9.1 or resolve all this stuff myself? Devs aren't really available for me to consult with since initial app was developed through full-service software dev company.
Im mainly in contact with business ops/project managers who don't really have knowledge of tech at this level. Im no seasoned dev myself so I'd like some advice here before expressing concerns with managers or getting strings pulled to talk with devs who last worked on it.
I'm hoping the first comment isn't that this question doesn't belong here. I think its a fine line.
Thanks for your time.
The app in the appstore could be submitted and released to the appstore with issues listed in the issue navigator of the xcode on posted screenshot.
So, switching to a version of Xcode which was used for a last submit to the app store by previous developers does not guarantee that those issues will be not present.
There is only one issue which you have to resolve is "1024x1024 app store icon is required for iOS app" and this can be done only within Xcode 9
This could be related to the problem here, but since this is happening in my iOS build (not Android), and I have cleaned the project and restarted Appcelerator, I don't know why this would occur.
Note - I did not change my dev environment, update appcelerator, or change any certs on my MBA where I'm developing my app. The only thing that I've changed is app code. I thought that I might see bugs or errors, but I'm not trying to debut either, as I'm building and installing via iTunes sync to my ipod Touch w/9.2. The build process and settings have not changed, so I don't even know where to start.
Work around more than an answer, but for some reason, my device, registered at apple was not being recognized by appcelerator (see note in my comment for related issue). After logging into apple dev center, and going back to appcelerator, the issue appeared to go away. I don't know if this is solved, but the workaround got me in business again.
Suddenly my ad-hoc distributions through Testflight and iTunes-sync no longer work. The application distributed using the ad-hoc build config never start fully on device. It crashes immediately with a segmentation fault 11.
The weird thing with this problem is that a debug build, on all the devices mentioned below, work flawlessly. This is causing me to believe that there is something messed up in my project.pbxproj. But when I look in the git-log I see nothing out of order, the only thing changed in there are the Architectures (ARCHS) and Valid Architectures (VALID_ARCHS).
Am I correct to assume that messing up the architectures should not cause an actual error on startup but during the build process?
Some Background:
Also worth mentioning is that I had both Xcode 4.4.1 and 4.5 GM installed, when I upgraded the GM to the one from App Store it removed my backup of Xcode 4.4.1 as well. After that hiccup I removed all version of Xcode, rebooted and installed version 4.4.1 again (this is so I can build for armv6).
Any helpful tips in how to proceed with this debugging is extremely valuable to me.
Thanks for your time.
<3
Console print and crash log from device:
- https://gist.github.com/3781018
I can add more logs if needed.
Current Environment:
- Xcode Version 4.4.1 (4F1003)
- Mac OS Version 10.8.2
Project Setup (pbxproj):
- https://gist.github.com/3780985
Devices tested:
- iPhone 3GS iOS 6
- iPhone 3G iOS 4.2.1
- iPad 2nd Gen iOS 5.1.1
- iPhone 4S iOS 5.1.1
- iPhone 4 iOS 6.0
- iPhone 4S iOS 6.0
Update
To proceed with the debugging this is what I tried:
1. Skip Testflight and use the old-school way of releasing an ad-hoc with iTunes. FAIL
2. Reinstalling the provisioning profiles FAIL
2. Create a new user on my machine an reinstall Xcode. FAIL
3. Build from another machine. FAIL
4. Set optimization level to: -O0 FAIL
Even though I was certain that none of the code had been changed, I saw no other reasonable explanation for this. So I started reverting the project in git, staring with the day I successfully made an ad-hoc release. To my horror I noticed that the same segmentation fault was following me through the fabric of time!
Considering this fact there was only one action left to take; a very powerful way of debugging I dubbed spray-and-pray. =) In other words I started to comment out sections of the code and see if that made any difference and to my complete surprise it actually did. After a few hours of disabling and enabling parts of my application I found the culprit: a static NSArray was never retained. What's really blowing my mind here is that the actual initialization of the array has been looking the same since 2010. So why on earth did this suddenly result in a memory error now? And why did the static analyzer not warn we about this?
I am too exhausted at the moment to answer those questions right now, I will try to update the question with more details and hopefully an answer as well tomorrow.
Once again, a big thank you for anyone who helped out so far! <3
It looks like the cause of the problem is the concurrency issue:
Crashed Thread: 1
In such a case it may be hard to find and resolve the root of the problem (http://en.wikipedia.org/wiki/Unusual_software_bug#Heisenbug).
May be you are doing something with one object from multiple threads without proper synchronization;
or may be you dealloc'ed object in one thread (ex. thread 0) and trying to access it from another (thread 1).