NSKeyedUnarchiver error after renaming Xcode project

Question

I just renamed my Xcode project and when I ran it I got this error:

2015-11-14 05:32:42.337 Buck Tracker[3537:1456100] * Terminating app due to uncaught exception 'NSInvalidUnarchiveOperationException', reason: '* -[NSKeyedUnarchiver decodeObjectForKey:]: cannot decode object of class (iBudgeter.Record) for key (NS.objects); the class may be defined in source code or a library that is not linked'

The Buck Tracker is the new name and iBudgeter is the original name. Record is a custom NSObject I created to store some data.

I tried renaming the project back to iBudgeter but it didn't work. Reverting to a previous version in git did help but I got the same error when I renamed it again.

So any suggestions?

Do you have existing users with stored data that you want to preserve access to? — rob mayoff, Nov 13 '15 at 21:45
@robmayoff yeah in fact reseting the simulator works but this app is already on App Store so I can't do that — hklel, Nov 13 '15 at 21:47

score 19 · Answer 1 · answered May 11 '16 at 12:36

19

another way is to fix the name of the class used for NSCoding. You simply have to use:

NSKeyedArchiver.setClassName("Record", forClass: Record.self before serializing
NSKeyedUnarchiver.setClass(Record.self, forClassName: "Record") before deserializing

wherever needed.

Looks like iOS extensions prefix the class name with the extension's name.

answered May 11 '16 at 12:36

teriiehina

4,741
3
41
63

I spent half a day on this. Thank you! – fluder Mar 05 '23 at 16:36

score 10 · Answer 2 · answered Aug 29 '17 at 15:24

10

In Case if you moved your file to another module, you would need to add additional information

NSKeyedArchiver.setClassName("OldModule.ClassName", for: ClassName.self)
NSKeyedUnarchiver.setClass(ClassName.self, forClassName: "OldModule.ClassName")

answered Aug 29 '17 at 15:24

tt.Kilew

5,954
2
33
51

1

This is the correct answer when modules changed or target was copied etc. Thanks man. – Onur Şahindur Oct 24 '19 at 14:35

score 5 · Accepted Answer · edited May 23 '17 at 10:31

5

Don't change your project name. Just change the display name. It's the "Bundle display name" entry in your Info.plist. You'll probably need to add the entry.

See this answer if you want to change the display name of an OS X app.

edited May 23 '17 at 10:31

Community

1
1

answered Nov 13 '15 at 21:58

rob mayoff

375,296
67
796
848

Wow you are life saver! Didn't know I can do that :D – hklel Nov 13 '15 at 22:05
How do you do this if you want to change the name not just on the display name? – dhruvm Jun 15 '16 at 03:56

score 2 · Answer 4 · answered Sep 09 '20 at 06:59

2

Just delete the old app and run it again works for me

answered Sep 09 '20 at 06:59

kamrul

59
4

score 0 · Answer 5 · answered Jan 30 '20 at 15:46

0

I had this issue last night. Sorted it after 3 hours investigating by simply changing the 'Product Name' (under Build Settings) back to the original value.

answered Jan 30 '20 at 15:46

Charlie S

4,366
6
59
97

score -1 · Answer 6 · answered Oct 28 '18 at 21:27

I had the same error after only renaming a ClassA that uses the NSCoding protocol to ClassB.

For me the problem was that I had used the ClassA in my UserDefaults. So there was the old name ClassA stored in the UserDefaults .plist.

When the Application was starting it tried to read the .plist and because there was a mismatch in the names the Application crashes.

Solution for me was just to delete the user defaults and run the app again and it worked.

To delete the defaults I used this command in terminal:

defaults delete buldle-identifier

NSKeyedUnarchiver error after renaming Xcode project

6 Answers6

Linked