Closed barzin144 closed 2 weeks ago
π @barzin144 Thanks for opening your issue here! If you find this package useful hit the starπ!
@barzin144 what version of react-native-keys, you are using?
I did not test this package on react-native@0.63.0
, can you provide me reproducable GitHub example so I can fix it quickly
expo prebuild also doesn't work can not find keys.*.json when I log Keys import from 'react-native-keys' it show other data like APPLICATION_ID BUILD_TYPE DEBUG instead
@chanphiromsok Expo support in this package is in progress, My question from you is, how do you manage different Xcode schemes and Android different variants?π
@chanphiromsok Expo support in this package is in progress, My question from you is, how do you manage different Xcode schemes and Android different variants?π
I haven't try on IOS yet I test only android π build IOS is time consuming for me machine
@barzin144 what version of react-native-keys, you are using? I did not test this package on
react-native@0.63.0
, can you provide me reproducable GitHub example so I can fix it quickly
I'm using verions 0.6.0 I've update classpath com.android.tools.build:gradle to 4.2.2, But it made me to update other packages after updating every thing I've succeed to build but when I've tried to run on simulator I've got the error like can't call method async...
@chanphiromsok how do you manage android variants?
buildTypes {
debug {
signingConfig signingConfigs.debug
applicationIdSuffix ".dev"
}
release {
// Caution! In production, you need to generate your own keystore file.
// see https://reactnative.dev/docs/signed-apk-android.
signingConfig signingConfigs.release
applicationIdSuffix ".lava"
minifyEnabled enableProguardInReleaseBuilds
proguardFiles getDefaultProguardFile("proguard-android.txt"), "proguard-rules.pro"
}
releasestaging {
initWith release
applicationIdSuffix ".dev"
matchingFallbacks = ['release']
}
}
@barzin144 i did not experience this error, can we both look it on zoom?
@chanphiromsok how do you manage android variants?
buildTypes { debug { signingConfig signingConfigs.debug applicationIdSuffix ".dev" } release { // Caution! In production, you need to generate your own keystore file. // see https://reactnative.dev/docs/signed-apk-android. signingConfig signingConfigs.release applicationIdSuffix ".lava" minifyEnabled enableProguardInReleaseBuilds proguardFiles getDefaultProguardFile("proguard-android.txt"), "proguard-rules.pro" } releasestaging { initWith release applicationIdSuffix ".dev" matchingFallbacks = ['release'] } }
I use expo config to inject in app build.gradle base on ENV. It would be good if you write expo plugin for this package π€
@chanphiromsok I was writing an expo plugin, but I am afraid that some packages also had been making Android build variants and my package also has been making build variants then we can get into conflict. what do you suggest?
@chanphiromsok I was writing an expo plugin, but I am afraid that some packages also had been making Android build variants and my package also has been making build variants then we can get into conflict. what do you suggest?
I have an idea but I can't write Regex -first read file app/build.gradle
This issue is stale because it has been open 365 days with no activity. Remove stale label or comment or this will be closed in 7 days.
This issue was closed because it has been stalled for 7 days with no activity.
Hi, I hope your doing well, I added react-native-keys to my project everything works find in ios, but for android I can't build the project and I've got this error