Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

FatalException *** -[__NSCFConstantString stringByAppendingString:]: nil argument -[NSPlaceholderString initWithCharactersNoCopy:length:freeWhenDone:] #51

Closed
owenkealey opened this issue May 19, 2020 · 5 comments
Assignees

Comments

@owenkealey
Copy link

Hi,

I have an app with about 800 users and the library works for 99% of people, but I saw this in Crashlytics today.
Screen Shot 2020-05-19 at 7 34 56 PM

Any thoughts? I can provide more info if needed.

@aboedo aboedo self-assigned this May 21, 2020
@aboedo
Copy link
Member

aboedo commented May 21, 2020

Is your app deleting NSUserDefaults? If so, that would explain the crash.
If that is the case, there are a couple of workarounds, like only deleting the keys your app uses, or configuring RevenueCat with a separate instance of NSUserDefaults. Let me know if this is your case and I can elaborate more.

@owenkealey
Copy link
Author

owenkealey commented May 21, 2020 via email

@aboedo
Copy link
Member

aboedo commented May 21, 2020

I see. My thinking is that there might be a plugin or something (or the app itself) that's deleting user defaults.
I'm working on #49, which will allow for a quick workaround for this issue on flutter. I'll keep you posted.
In the meantime, are you using any plugins like shared_preferences that might be causing this?

@owenkealey
Copy link
Author

owenkealey commented May 21, 2020 via email

@aboedo
Copy link
Member

aboedo commented May 21, 2020

thanks for the info. That one should be safe, since it internally uses the keychain for storage (from their docs).
I'm not sure what might be causing NSUserDefaults getting cleared in your case, but I'll let you know as soon as I get the workaround out.
in #49 there's another workaround that might help, although that one involves a bit more work on the dev side

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants