CODEWITHSUNDEEP
ios8arm64
aledalgrande
aledalgrande

Reputation: 5217

Packaging error when switching to arm64 (arm5 was OK)

I just plugged in a new iPhone 6, created a provisioning profile and then I launched the app I'm developing on the device. It compiled fine, but at linking stage it errored out with:

ProcessProductPackaging

...

error: class '(null)' of input object does not respond to either selector writeToFile:options:error: or writeToFile:atomically

I cannot find any information of what that is. I do not get any specific code reference to relate it to. Did anyone experience this?

Upvotes: 12

Views: 4917

Answers (9)

Jurgis Lietunovas
Jurgis Lietunovas

Reputation: 67

Restarted XCode and enabled and disabled to Automatically manage signing

Upvotes: 0

David Cespedes
David Cespedes

Reputation: 517

I had the same problem specifically on an App Extension we used for Push Notifications, and I was using Automatically manage signing but it seems the App Groups in capabilities were failing, so I just had to make sure the App Groups were retrieved correctly and this fix it.

Also if you have .entitlements files, and you have App Groups there, make sure they are the same you are using in the capabilities configuration.

Upvotes: 0

John
John

Reputation: 8548

The error occurred after I made manual changes to the Xcode .entitlements and Info.plist files: I removed some entries. None of the above mentioned solution attempts worked for me. Every try to create an archive failed.

The solution was to go to Xcode's Capabilities section and switched everything on and off again.

Upvotes: 0

Martin
Martin

Reputation: 4765

I've tried turning the "Automatically managed signing" off and on again, then the issue disappeared. Note: rebuilding didn't help for me, cleaning either.

Upvotes: 2

DaisyLiang
DaisyLiang

Reputation: 21

I just restarted Xcode then the error was disappeared

Upvotes: 2

Neeraj Joshi
Neeraj Joshi

Reputation: 769

Rebuilding the project does the job for me. Actually I was making changes in capabilities while Xcode was building that makes build failed.

Upvotes: 1

Deepraj Chowrasia
Deepraj Chowrasia

Reputation: 1359

I just changed some provisioning setting and then restarted the xcode afterwards the error was disappeared and archived and then uploaded successfully

Upvotes: 1

jdero
jdero

Reputation: 1817

Personally I was able to solve this issue by rebuilding the project a second time. I think I was only experiencing it after revoking and requesting a certificate.

Odd for it to jump at me and disappear though.

Upvotes: 12

aledalgrande
aledalgrande

Reputation: 5217

I removed an external library and related code I had and it's now working.

Upvotes: 1

Related Questions