Closed sumerpatel closed 4 years ago
if you update and start having problems, always try npx react-native-clean-project
first to blow out any of the caches that might have stale version code in them
this didn't work
How did it work when you cloned this repo and used the example? If it works, your local project has a problem, but the module is fine, and it's not a bug, it's a project problem you'll have to figure out
@sumerpatel what is RN version, Platform ios? android? and OS version?
@sahil290791 RN : 0.61.5, Platform - Android, OS version - 10
The same error with: Android 28, 29, R react-native: 0.59.10
How did it work when you cloned this repo and used the example?
i had the old bundle and map files in:
android/app/src/main/assets/index.android.bundle
android/app/src/main/assets/index.android.map
after recreating those files start working again
react-native bundle --platform android --dev false --entry-file index.js --bundle-output android/app/src/main/assets/index.android.bundle --sourcemap-output android/app/src/main/assets/index.android.map --assets-dest android/app/src/main/res/
@NaNtrack do not do that! Never copy built assets into the src tree.
This was the source of many problems, a PR directly into react-native, and then a revert of that PR. There is a correct way to do the bundle, and this is it: https://github.com/facebook/react-native/issues/22234#issuecomment-504721069
we dont have those files versioned on git, so no worries...
we dont have those files versioned on git, so no worries...
If you read that thread you'll realize it causes problems in local builds frequently, like you experienced. I also had those files .gitignore'd but it still blows up your local environment and/or masks changes you make (like software version upgrades).
If that's how you want to develop, okay, but given there's a posted solution that works and the way you're doing it (and the way I was doing it) was conclusively shown to be wrong, seems odd to want to keep doing it.
we dont have those files versioned on git, so no worries...
If you read that thread you'll realize it causes problems in local builds frequently, like you experienced. I also had those files .gitignore'd but it still blows up your local environment and/or masks changes you make (like software version upgrades).
If that's how you want to develop, okay, but given there's a posted solution that works and the way you're doing it (and the way I was doing it) was conclusively shown to be wrong, seems odd to want to keep doing it.
thanks for the advice, we will find a better solution to avoid this problem in the future
How did it work when you cloned this repo and used the example?
Created a new RN project with version 0.61.5 and it still didn't work.
new project != clone repo + use example, I'm very curious if the example in this repo works if it does, then what is the difference between the example and a fresh project?
After updating react-native-fingerprint-scanner package to latest version android app started getting crashed. Attached a screenshot of the error.
Here is my code : -
error: ReactNativeFingerprintScanner.authenticate got 2 arguments, expected 3