SetItem never resolves in Samsung A72 device
See original GitHub issueFirst of all, this is my workspace:
"react": "16.13.1",
"react-native": "0.63.3",
"react-native-sensitive-info": "^5.5.8",
Android version: 11
I tried the same sample in ASUS Zenfone 3 Max (Android 8) and it worked just fine, but when I try it in Samsung A72 device, the SetItem function never resolves.
console.log('before');
try {
await RNSInfo.setItem('testone', 'Pass123123', {
touchID: true,
showModal: true,
kSecAccessControl: 'kSecAccessControlBiometryAny',
});
} catch (er) {
console.log({ er });
}
console.log('after');
OUTPUT:
>before
it does not throw errors, neither resolves 😦 Android native modal also does not show.
Issue Analytics
- State:
- Created 2 years ago
- Reactions:1
- Comments:6
Top Results From Across the Web
Galaxy A72 | Samsung Support UK
Galaxy A72. Solutions & Tips, Download Manual, Contact Us. Samsung Support UK.
Read more >Samsung Galaxy A72 | Samsung Australia
If awesome is what you want, meet the Galaxy A72. It features 6.7" FHD+ Super AMOLED Display, advanced 64MP Camera with OIS, IP67...
Read more >A72/ 2021 settings - Samsung Community
Hey! I've got some issues with my Phone,but the most important is that I cant find factory reset for it in my settings,I...
Read more >Nougat OS: How to change premium SMS settings to allow ...
FAQ for Samsung Mobile Phone. ... with Samsung Support. ... 6 Choose between the 3 options (Ask - Never allow - Always allow)...
Read more >Galaxy A72 goes in bootloop after latest july security patch ...
1. Factory data reset the phone. If not resolved. · 2. Install the official firmware. If still not resolved · 3. Enter recovery...
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
This appears to be resolved if I backport https://github.com/mCodex/react-native-sensitive-info/pull/238 to
5.5.8
I see that it was pulled into the
v5.x
branch: https://github.com/mCodex/react-native-sensitive-info/commit/16512f69ee8bc83f55113b9fe0d4d3f65e8b216e but might not have been released.I can maintain a patch on my side, but @mCodex would it be possible to get a patch release out for the head of the
v5.x
branch? Or, is the v6 release coming on the horizon?This still seems to be an issue Samsung Galaxy A32 Android 11