App crashing:unrecognized selector sent to instance
See original GitHub issueiOS versions: 11.3 and 11.4 react-native-sensitive-info versions: 5.1.0
My code
const keyNameSpace = {
sharedPreferencesName: 'xyz',
keychainService: 'xyz',
};
const migrationDone = await SInfo.getItem('migrationDone', keyNameSpace);
Exception logs
RCTFatalException: Exception '-[__NSSingleObjectArrayI localizedDescription]: unrecognized selector sent to instance 0x1c02081a0' was thrown while invoking getItem on target RNSensitiveInfo with params ( migrationDone, { keychainServic: Exception '-[__NSSingleObjectArrayI localizedDescription]: unrecognized sel...
Issue Analytics
- State:
- Created 5 years ago
- Reactions:2
- Comments:9 (4 by maintainers)
Top Results From Across the Web
Unrecognised selector sent to inst… | Apple Developer Forums
Unrecognised selector sent to instance causing app crash Ok so after the user fills out their details in the Sign in view controller...
Read more >App crashes when i run with this error "unrecognized selector ...
I'm using a segment controllers for show tableview , I want Underline for selected index, This is my function , I don't know...
Read more >App crashing immediately [FBLPromise HTTPBody ... - GitHub
... app due to uncaught exception 'NSInvalidArgumentException', reason: '-[FBLPromise HTTPBody]: unrecognized selector sent to instance ...
Read more >Fatal Exception: NSInvalidArgumentException -[NSNull length]
-[NSNull length]: unrecognized selector sent to instance 0x1b78ee650 in iOS Crash ... I have received this error in iOS crashes. No issues over...
Read more >How to debug 'unrecognized selector send to instance' | Medium
In most of the cases Xcode do not take us to the exact line where this issue happen. When app crash you won't...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
The pre-release is dated back to October '17 and there is a newer version (5.2.1), so the package should be updated on npm, right? @mCodex
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.