Google Resolver can not run with OneSignal 2.7.5, Firebase 5.2.1, & play-services-resolver-1.2.88.0+ #146
Comments
|
Here is another log trace Refresh: detecting if any assets need to be imported or removed ... Failed to run '/Users/imac/bitbucket/CleanBuild/Temp/PlayServicesResolverGradle/gradlew -b "/Users/imac/bitbucket/CleanBuild/Temp/PlayServicesResolverGradle/PlayServicesResolver.scripts.download_artifacts.gradle" --no-daemon "-PANDROID_HOME=/Users/imac/Library/Android/sdk" "-PTARGET_DIR=/Users/imac/bitbucket/CleanBuild/Assets/Plugins/Android" "-PMAVEN_REPOS=file:////Users/imac/bitbucket/CleanBuild/Assets/Firebase/m2repository" "-PPACKAGES_TO_COPY=com.google.firebase:firebase-analytics:16.0.1;com.google.firebase:firebase-core:16.0.1;com.google.firebase:firebase-iid:[17.0.0];com.google.firebase:firebase-analytics-unity:5.2.1;com.google.android.gms:play-services-base:15.0.1;com.google.firebase:firebase-common:16.0.1;com.google.firebase:firebase-app-unity:5.2.1;com.google.firebase:firebase-messaging:17.3.0;com.google.firebase:firebase-messaging-unity:5.2.1;com.google.android.gms:play-services-base:[10.2.1, 12.1.0);com.google.firebase:firebase-messaging:[10.2.1, 12.1.0);com.google.android.gms:play-services-location:[10.2.1, 12.1.0);com.android.support:support-v4:[26.0.0, 27.2.0);com.android.support:customtabs:[26.0.0, 27.2.0)"'
stderr: FAILURE: Build failed with an exception.
BUILD FAILED in 13s exit code: 1 UnityEngine.DebugLogHandler:Internal_Log(LogType, String, Object) (Filename: /Users/builduser/buildslave/unity/build/Editor/Mono/EditorApplication.cs Line: 127) Resolution failed Failed to fetch the following dependencies: UnityEngine.DebugLogHandler:Internal_Log(LogType, String, Object) (Filename: /Users/builduser/buildslave/unity/build/Editor/Mono/EditorApplication.cs Line: 127) Refresh: detecting if any assets need to be imported or removed ... Refresh: elapses 0.011532 seconds (Nothing changed) |
|
@takaaptech Thanks for the full log! Looks like this might be an issue with the Google unity-jar-resolver plugin. Can you open a new issue on their repo providing your |
|
Hi @jkasten2 https://drive.google.com/file/d/1kqTfGUUGtZ06VeShejKz7yPKEC89MoNo/view?usp=sharing Here is the AndroidResolverDependencies content |
|
@takaaptech Sorry, I edited my post just after I posted it and re-read you already tried updating that. Can you create an issue on their tracker? Some how it is trying to resolve a version that does not exists such as this one> |
|
Ok here is it googlesamples/unity-jar-resolver#149 |
|
@takaaptech I am having the same exact problem. It keep complain about version 12.1.0+. Did you get it resolve ? |
|
@takaaptech I haven't, but I believe the issue is due to the unity-jar-resolver. Reply back here if they need more help on the issue and I can jump in. |
|
@c00piser Not yet, I will post back here if we have a solution for this. |
|
Same for me with onesignal and admob (are you sure that the problem does not come from you ? because if I use old "release" of one signal, I have no problem) |
* Changed version range dependencies to use '[' instead of '(' due to a bug with play-services-resolver 1.2.88.0+
* This relates to issue googlesamples/unity-jar-resolver#151
* This resolves #146
jkasten2
changed the title
|
@takaaptech I was able to reproduce the issue locally. It is due to some bugs introduced with I have created PR #152 to fix this compatibility as a work around, and have created issue googlesamples/unity-jar-resolver#151 on the Google's repo to fix the root of the issue. This will be included in the next release but until then you can manually update Thanks. |
|
Thank you very much, that works !
Le ven. 21 sept. 2018 à 03:42, Josh Kasten <notifications@github.com> a
écrit :
… @takaaptech <https://github.com/takaaptech> I was able to reproduce the
issue locally. It is due to some bugs introduced with
play-services-resolver-1.2.88.0 with some specific scenarios, I have
updated the title to include this.
I have created PR #152
<#152> to fix this
compatibility as a work around, and have created issue
googlesamples/unity-jar-resolver#151
<googlesamples/unity-jar-resolver#151> on the
Google's repo to fix the root of the issue.
This will be included in the next release but until then you can manually
update Assets/OneSignal/Editor/OneSignalDependencies.xml with the
following contains.
https://github.com/OneSignal/OneSignal-Unity-SDK/pull/152/files
Thanks.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#146 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ANhwEs_QTnR4etbMk2vCypdMIv8uK3lQks5udEQUgaJpZM4Wi1dM>
.
|
* Changed version range dependencies to use '[' instead of '(' due to a bug with play-services-resolver 1.2.88.0+
* This relates to issue googlesamples/unity-jar-resolver#151
* This resolves #146
|
@jkasten2 Thanks! |
|
@agrobost Your code can be simplified, the OneSignal SDK remembers if you called void YourAppInitMethod() {
// SetRequiresUserPrivacyConsent will prevent
// initialization until UserDidProvideConsent(true) is called
OneSignal.StartInit("YOUR_APP_ID")
.SetRequiresUserPrivacyConsent(true)
.EndInit();
}
void UserAcceptedConsent() {
// Only needs to be called once,
// OneSignal will remember the last answer
OneSignal.UserDidProvideConsent(true);
}We just updated our docs to clear this up with the above code too. If you have follow up questions please open a new issue or contact OneSignal support about this issue. We would like to keep issues on a single topic to avoid confusion. I am not sure I understand your "Google play crash with last unity version" issue. Please open an another issue separate from either of these if it is related to OneSignal. |
|
Thank you for these explanations. Is it possible to set UserDidProvideConsent to false after initialization? OneSignal.StartInit("YOUR_APP_ID")
.SetRequiresUserPrivacyConsent(true)
.EndInit();
OneSignal.UserDidProvideConsent(true);
//Call after
void UserWithdrawsHisConsent() {
OneSignal.UserDidProvideConsent(false);
}Or it only takes effect at oneSignal initialization ? EDIT: I check with tests, that only works at the initialization |
|
@agrobost If you have a way for the user to revoke their acceptance for any reason you can call I recommend contacting OneSignal support for any additional questions on this topic. |
|
After solving this i get a warning in unity. build not working Some conflicting dependencies were found. UnityEngine.Debug:LogWarning(Object) |
Status from @jkasten2:
Issue is is due to Google's
unity-jar-resolver, a ticket has been opened under googlesamples/unity-jar-resolver#149 to fix this issue.Workaround fix in PR #152, this will be included in the next release.
Orignal message:
Hi,
Please help, I am having a problem when trying to Force resolve
One signal 2.7.5
Unity 2017.4.4f1
Firebase Analytics 5.2.1
play-services-resolver-1.2.89.0
Android sdk update to max
Java sdk 1.8
When trying to Force Resolve, We have the problem
Without One signal, the Resolve works well.
Thank so much
Gradle failed to fetch dependencies.
Failed to run '/Users/imac/Downloads/1943RevolutionTeam/Temp/PlayServicesResolverGradle/gradlew -b "/Users/imac/Downloads/1943RevolutionTeam/Temp/PlayServicesResolverGradle/PlayServicesResolver.scripts.download_artifacts.gradle" --no-daemon "-PANDROID_HOME=/Users/imac/Library/Android/sdk" "-PTARGET_DIR=/Users/imac/Downloads/1943RevolutionTeam/Assets/Plugins/Android" "-PMAVEN_REPOS=file:////Users/imac/Downloads/1943RevolutionTeam/Assets/Firebase/m2repository" "-PPACKAGES_TO_COPY=com.android.support:support-v4:25.3.1;com.android.support:appcompat-v7:25.3.1;com.android.support:cardview-v7:25.3.1;com.android.support:customtabs:25.3.1;com.google.firebase:firebase-analytics:16.0.1;com.google.firebase:firebase-core:16.0.1;com.google.firebase:firebase-iid:[17.0.0];com.google.firebase:firebase-analytics-unity:5.2.1;com.google.android.gms:play-services-base:15.0.1;com.google.firebase:firebase-common:16.0.1;com.google.firebase:firebase-app-unity:5.2.1;com.google.firebase:firebase-messaging:17.3.0;com.google.firebase:firebase-messaging-unity:5.2.1;com.google.android.gms:play-services-base:[10.2.1, 12.1.0);com.google.firebase:firebase-messaging:[10.2.1, 12.1.0);com.google.android.gms:play-services-location:[10.2.1, 12.1.0);com.android.support:support-v4:[26.0.0, 27.2.0);com.android.support:customtabs:[26.0.0, 27.2.0)"'
stdout:
com.google.android.gms:play-services-base conflicting due to package(s):
com.google.android.gms:play-services-basement conflicting due to package(s):
com.google.android.gms:play-services-stats conflicting due to package(s):
com.google.android.gms:play-services-tasks conflicting due to package(s):
com.google.firebase:firebase-analytics conflicting due to package(s):
com.google.firebase:firebase-analytics-impl conflicting due to package(s):
com.google.firebase:firebase-common conflicting due to package(s):
com.google.firebase:firebase-iid-interop conflicting due to package(s):
com.google.firebase:firebase-measurement-connector conflicting due to package(s):
Resolution attempt: 1, conflicts detected: true, updated packages: true
Resolution attempt 2: packages [com.android.support:customtabs:26.1.0, com.google.firebase:firebase-common:16.0.1+, com.google.android.gms:play-services-base:15.0.1+, com.android.support:cardview-v7:26.1.0, com.android.support:support-media-compat:26.1.0, com.android.support:support-vector-drawable:26.1.0, com.google.android.gms:play-services-location: 12.1.0+, com.android.support:support-fragment:26.1.0, com.android.support:animated-vector-drawable:26.1.0, com.android.support:support-annotations:26.1.0, com.google.firebase:firebase-core:16.0.1+, com.google.firebase:firebase-analytics-unity:5.2.1@srcaar, com.google.firebase:firebase-messaging:17.3.0+, com.android.support:support-core-utils:26.1.0, com.android.support:appcompat-v7:26.1.0, com.android.support:support-compat:26.1.0, com.android.support:support-v4:26.1.0, com.google.firebase:firebase-app-unity:5.2.1@srcaar, com.google.firebase:firebase-messaging-unity:5.2.1@srcaar, com.google.firebase:firebase-analytics:16.0.1+, com.google.firebase:firebase-iid:[17.0.0], com.android.support:support-core-ui:26.1.0]
Resolve failed due to com.google.android.gms:play-services-location: 12.1.0+ missing for project :, attempted to use com.google.android.gms:play-services-location: 12.1.0+, failed due to org.gradle.internal.resolve.ModuleVersionNotFoundException: Could not find any version that matches com.google.android.gms:play-services-location: 12.1.0+.
Versions that do not match:
Searched in the following locations:
stderr:
FAILURE: Build failed with an exception.
Where:
Build file '/Users/imac/Downloads/1943RevolutionTeam/Temp/PlayServicesResolverGradle/PlayServicesResolver.scripts.download_artifacts.gradle' line: 745
What went wrong:
A problem occurred evaluating root project 'PlayServicesResolverGradle'.
Try:
Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output. Run with --scan to get full insights.
Get more help at https://help.gradle.org
BUILD FAILED in 12s
exit code: 1
The text was updated successfully, but these errors were encountered: