Open geekmidas opened 3 years ago
Hi @geekmidas do you have some news about this? Typically this kind of problem means some problem in the configuration of the project with maybe a wrong SHA-1. Please also note that the SAH-1 is normally different from debug to release
@Francesco-Voto I do not, I struggled and we postponed the feature for later. How did you set yours up?
For testing we add the debug SHA1. Typically you can find it in this way
keytool -list -v -keystore ~/.android/debug.keystore -alias androiddebugkey -storepass android -keypass android
.
Remember to change with your production keystore and also test it with a release build.
this is happening for us too.
hi, I am also facing that issue so I try another library. there I found a comment help i am able to resolve this issue please check. in app/build.gradle.
signingConfigs {
/* debug {
storeFile file('...')
storePassword '...'
keyAlias '...'
keyPassword '...'
} */
...
}
in your_project/android delete debug.keystore after complete this step clean and unsitall app then run again.
https://github.com/StasDoskalenko/react-native-google-fit/issues/215#issuecomment-784046957
Below is the code that I am using. When I call
requestPermissions
it does not ask the user for permissions. Please assist