Reputation: 996
After updating Xcode 14.0 when I try to distribute application as adhoc or developer, from the Xcode organizer I get the Error like
"The operation couldn’t be completed. (AppThinning.StubError error 1.)"
But when I select upload application on the app store or try to export app for the app store its working fine and upload app on the app store.
Please suggest me what the issue this and if any know the solution then please guide.
Upvotes: 22
Views: 13836
Reputation: 11
Clear your storage or archive, and check again. Hope this will solve the issue.
Upvotes: 1
Reputation: 9
"I successfully addressed the bug by optimizing storage space on my MacBook."
Upvotes: 0
Reputation: 1108
Running
brew install sqlite 3
and then restartarting XCode worked for me.
Upvotes: 0
Reputation: 1
I was getting this error working with React Native. For some reason xcode built-in ruby needs sqlite3 when I try to distribute my app (exporting an IPA file). But when I ran sudo gem install sqlite3
I got a ruby version compatibility error. Here's how I fixed it:
ruby --version
and it will output something like thisruby 2.6.10p210 (2022-04-12 revision 67958) [universal.x86_64-darwin22]
Look at the value inside the [
]
. That is the platform for your local machine. In my case it's universal.x86_64-darwin22
Install sqlite3
for this specific platform by running
sudo gem install sqlite3 --platform universal.x86_64-darwin22
Good luck!
Upvotes: 0
Reputation: 11
for me it was because of low storage. I deleted unnecessary things and restarted the Xcode.then after having enough space, it worked for me
Upvotes: -1
Reputation: 69
I met a similar issue, and I solved like below: Click apple icon on the top left of screen > About this Mac > Storage > Manage > Developer and Open the screen, delete all cache, then it should work well.
Upvotes: 0
Reputation: 702
I installed sqlite3, and set to use system default.
$ sudo gem install sqlite3
$ rvm use system --default
I referenced below.
https://blog.csdn.net/RreamigOfGirls/article/details/128146944
Upvotes: 3
Reputation: 1895
You can use this trick:
After press next button
before having the error:
I pressed repeatedly Enter(Return) button on the keyboard and It passes the error.
I could have an ad-hoc IPA
Upvotes: 24
Reputation: 756
I have fixed the issue by running sudo gem install sqlite3
You may need to restart your computer after the installation
The reason is because of this line in the IDEDistribution.verbose.log
file
/System/Library/Frameworks/Ruby.framework/Versions/2.6/usr/lib/ruby/2.6.0/rubygems/core_ext/kernel_require.rb:130:in require': cannot load such file -- sqlite3/sqlite3_native (LoadError)
It may be happening because you installed another version of ruby, causing sqlite3 to be missing
More info here
Upvotes: 2
Reputation: 41
In my case, (Maybe install older version XCode 13.4.1 is not needed.) I install older version XCode 13.4.1, and distribute application as adhoc again, then still show "The operation couldn’t be completed. (AppThinning.StubError error 1.)", I Click Show Logs, it will open logs folder. Open IDEDistribution.standard.log file, then I saw the error: `require': cannot load such file -- sqlite3/sqlite3_native (LoadError)
So I search keyword and find this article. https://github.com/sparklemotion/sqlite3-ruby/issues/240
I try these SUDO Command:
gem uninstall sqlite3 --all
ridk exec pacman -S mingw-w64-x86_64-sqlite3
gem inst sqlite3 --platform ruby
Then distribute application as adhoc again, distribute Successful! Now you can back to XCode 14.1, and work fine again.
Upvotes: 4
Reputation: 993
This was broken for me on Xcode 14.0.1 but seems to be working on Xcode 14.1. I'm not sure if it's random luck, or actually fixed, as it's not mentioned in the release notes that I could find.
Upvotes: 1
Reputation: 11
In my case, starting Xcode with Rosetta let me do the Ad-Hoc distribution
Upvotes: 1
Reputation: 1
Hi These Error may occur due to low storage space remaining on your MacBook. Free Some storage space and try again.
Upvotes: 0
Reputation: 51
Disabling bitcode worked for me. This is probably with an internal change apple made for ad-hoc builds or an error. I hope it's the latter.
Upvotes: 0