Hi, Since I updated my mac air M1 bigsur to Monterey 12.0.1 I can't upload the .IPA file with transporter app. The app is verified and then at the beginning of the distribution it stoped to upload. The computer then crashed 5-10 minutes later, in the meantime only basic navigation is possible (finder..). I tried 5 times with the same issue. I Tried to reinstall transporter.
Crash report:
Well, that’s not good. See as there are only Apple components involved here, you should definitely file a bug about this.
Make sure to include a sysdiagnose log. If you can trigger one when the Mac is hung, that’d be grand. If not, do it after the restart.
Please post your bug number, just for the record.
Do you seem the same problem with altool?
Share and Enjoy
—
Quinn “The Eskimo!” @ Developer Technical Support @ Apple
let myEmail = "eskimo" + "1" + "@" + "apple.com"
Thank you for your answer. I couldn't use altool as Xcode was not up to date on my Mac. When i tried to update Xcode, it didn't work either (the download was ok but the install of the app would never end).
I ended up re-installing the Monterey OS and it works now...
any one have solution for this problem ? i'm using transporter to, but my mac always freeze and restart, if transporter doing distribution file.. it's make me frustating, and if upload my application through xcode, that is like forever upload, not network activity but still status uploading.. my mac M1 2020, MacOS Monterey 12.0.1
Same problem here on Macbook M1 2020 Monteray 12.0.1
Hi everyone! I have the same problem!
I was trying to upload my build to apple via Xcode as I normally do, but the process stopped due to this error “AppStore connect operation error part (number) failed to upload. The request timed out”. So i did a second try and Mac started to freeze and eventually reboot itself.
Then I did a try with Transporter but the same thing happened….
is there any solution? Thanks
Hello everyone I have the same issue on Macboock pro m1 2020 Monterey 12.1!
I was trying to upload my app via transporter as normally, but the process stops each time it reaches the uploading status. Then, after a few minutes the computer crashed and restarted.
Is there any solution for this?
I am too having the same problem on Macboock air m1 2020 Monterey 12.0.1
Hi there! I just did another try with transporter and.... it worked perfectly!!
I didn't change anything since last time so, I'm 99% confident it was a Apple problem: somehow, communication with AppStore Connect was returning some error that Mac couldn't handle, hence the reboots...
I'm having the same issue on my MacBook Air M1. Every time I try to upload a .ipa using transporter, my MacBook loses network connectivity (Despite saying I'm connected) and I have to forcibly restart it. I tried many times, I uninstalled the transporter app but the issue persists. Any solution ? I'd like to solve this without having to reinstall the OS.
still happens in macos monterey 12.2.1, and with latest version of transporter, in macbook air m1 2020
I'm glad I'm not alone but is there not yet an answer to this problem?!
I am using Monterey 12.2.1, Transporter 1.2.3.
Same problem, Transporter appears to freeze when UPLOADING APP when I am uploading any large (for example my TFFast app is 200MB, my little apps go up fine). Then my whole Mac freezes up. I either hard-reboot (no response from Force Quit) or if you leave the Mac a while, it reboots and gives the following message when reopening Transporter:
Package (s) cannot be found. The following package could not be found: /var/folders/.... 1217478123-01-038.156.01-1.itmsp. They will be deleted from the queue.
iCloud has been updating very slowly recently?! Could there be a relationship between ability to upload using Transporter and iCloud sync status?
Please help us Quinn the Eskimo!
FB9952962 (Transporter crashes when UPLOADING APP) Submitted via Apple Developer Feedback Assistant. Quinn kindly also advised : "Transporter is supported by App Store Connect Support rather than DTS. You can contact them by going to the main contact page and then clicking App Setup and Distribution > Binary Delivery and Processing." I have opened a Case with Support and will let you guys all know how I get on! Wish me luck!
I have the same issue. It happens on Xcode and transporter. I have tried 3 times, it was all failed. Any solution about this?
unbelivable that this is not fixed till now
Having the save issue pls fix this :(
I have the same issue with Monterey 12.3.
I have the same problem.
Crash report:
Attempting to forcibly halt cpu 1
cpu 1 failed to halt with error -5: halt not supported for this configuration
Debugger synchronization timed out; waited 240000 nanoseconds
panic(cpu 3 caller 0xfffffe002a1266d8): thread_call group 'high' reached max thread cap (500): active: 1, blocked: 499, idle: 0 @thread_call.c:409
Debugger message: panic
Memory ID: 0xff
OS release type: User
OS version: 21E258
Kernel version: Darwin Kernel Version 21.4.0: Fri Mar 18 00:47:26 PDT 2022; root:xnu-8020.101.4~15/RELEASE_ARM64_T8101
Fileset Kernelcache UUID: E642C8E63C1D004A6B6639342D386514
Kernel UUID: 79A2DE0A-5FBB-32B8-B226-9D5D3F5C25A4
iBoot version: iBoot-7459.101.3
secure boot?: YES
Paniclog version: 13
KernelCache slide: 0x00000000227ec000
KernelCache base: 0xfffffe00297f0000
Kernel slide: 0x0000000022f8c000
Kernel text base: 0xfffffe0029f90000
Kernel text exec slide: 0x0000000023074000
Kernel text exec base: 0xfffffe002a078000
mach_absolute_time: 0x4a7a8c35e
Epoch Time: sec usec
Boot : 0x6263008e 0x00022a34
Sleep : 0x00000000 0x00000000
Wake : 0x00000000 0x00000000
Calendar: 0x626303c9 0x000c2f37
...
Monterey v12.3.1
All software up-to-date, reinstalled Transporter. No luck.
Any ideas what to do?
same here. computer gets unresponsive. osx m1. any sugestions ?
still happening with macos monterey v 12.4
Still happen on me for Monterey 12.4
Still happening on my M1 mac running latest all software. I use my intel based Mac to submit after I airdrop the IPA file over.
I also reported this to Apple support a long time ago. They followed up briefly then completely ignored the ticket.
It seems the same is happening to others.
The level of support for a fault of this magnitude is pathetic and we (developers) except a lot more, especially considering the amount of revenue Apple makes from developers.