-
Notifications
You must be signed in to change notification settings - Fork 212
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
release apk error :onesignal:verifyReleaseResources #61
Comments
Hello, try adding
to your project's android/build.gradle |
@rgomezp Unfortunately I had no luck here is my buildscript {
repositories {
google()
jcenter()
maven { url 'https://plugins.gradle.org/m2/' }
}
dependencies {
classpath 'com.android.tools.build:gradle:3.3.1'
classpath 'com.google.gms:google-services:4.2.0'
}
}
allprojects {
repositories {
google()
jcenter()
}
}
rootProject.buildDir = '../build'
subprojects {
project.buildDir = "${rootProject.buildDir}/${project.name}"
}
subprojects {
project.evaluationDependsOn(':app')
project.configurations.all {
resolutionStrategy.eachDependency { details ->
if (details.requested.group == 'com.android.support'
&& !details.requested.name.contains('multidex') ) {
details.useVersion "27.0.1"
}
}
}
}
subprojects {
afterEvaluate {project ->
if (project.hasProperty("android")) {
android {
compileSdkVersion 28
buildToolsVersion "28.0.2"
}
}
}
}
task clean(type: Delete) {
delete rootProject.buildDir
} |
Had the same issue. @rgomezp's solution did not work for me also.
|
@TarekkMA can you try jooseplall's workaround? |
@Nightsd01 -- Brad & co. I am a paying one signal customer and this is blocking (except maybe for the work around) us from releasing our next version of our app. You need to make a 1.1.0 (I think this is sort of a breaking change?) to update to AndroidX (api 28) since Flutter beta is now dependent on it. Flutter Doctor ] Flutter (Channel beta, v1.2.1, on Mac OS X 10.14.3 18D109, locale en) |
@jooseplall -- Any problem with us using your fork (and can you submit a PR?) while we wait for OneSignal to update the official package? And thank you! That works perfectly! |
@sjmcdowall @jooseplall Thanks for the details. We have updated the We plan on releasing an SDK update with this included later this week. You can use the master of this repo directly in your Thanks. |
Great gnus!
:)
… On Mar 4, 2019, at 10:07 PM, Josh Kasten ***@***.***> wrote:
@sjmcdowall <https://github.com/sjmcdowall> @jooseplall <https://github.com/jooseplall> Thanks for the details. We have updated the compileSdkVersion to 28 in this commit and it is in master.
40d9730 <40d9730>
We plan on releasing an SDK update with this included later this week. You can use the master of this repo directly in your pubspec.yml to work around the issue today:
https://github.com/OneSignal/OneSignal-Flutter-SDK.git <https://github.com/OneSignal/OneSignal-Flutter-SDK.git>
Thanks.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub <#61 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AB8M7ZXrv2xkoJKyNd6sWbb-I-3xhKtiks5vTd9ogaJpZM4bEOwU>.
|
We just released OneSignal-Flutter-SDK 1.1.0 which includes Thanks. |
Appears to work just fine -- thanks!
… On Mar 11, 2019, at 5:48 PM, Josh Kasten ***@***.***> wrote:
We just released OneSignal-Flutter-SDK 1.1.0 <https://github.com/OneSignal/OneSignal-Flutter-SDK/releases/tag/1.1.0> which includes compileSdkVersion set to 28 now.
Updating should solve this issue after resyncing gradle in Android Studio and doing a clean build.
Thanks.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub <#61 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AB8M7VaMW-A7OrqgiAlimnfKE83WrUdLks5vVs9FgaJpZM4bEOwU>.
|
Description:
I get the following error after I run the release build command
flutter build apk --release -v
Environment
Anything else:
pubspec.yaml
app/build.gradle
The text was updated successfully, but these errors were encountered: