[Production] Failed to Sign In to host "openrainbow.com" (Android SDK)
RéponduThe only important message I found was this snippet from the debug logcat:
08-30 01:06:24.571 11351-11427/com.wasdlabs.
Then I copied the whole activity and layout into a new project, and ran it, and found out the sign in attempt was a success. I would like to inquiry about what would be the cause of the sign in failure. Was it my dependencies? Or something else?
Had double checked my extended Application class, no problem since I copied the whole App ID and Secret from the problematic app into the working test app and the test app worked just fine.
Here are my dependencies on App level build.gradle:
// Glide
implementation('com.github.bumptech.glide:glide:4.7.1') {
exclude group: "com.android.support"
}
// Picasso
implementation 'com.squareup.picasso:picasso:2.71828'
// File Picker
implementation 'com.droidninja:filepicker:2.1.5'
// PhotoView
implementation 'com.github.chrisbanes:PhotoView:2.1.3'
// ChatKit
implementation 'com.github.stfalcon:chatkit:0.2.2'
// ButterKnife
implementation 'com.jakewharton:butterknife:8.8.1'
annotationProcessor 'com.jakewharton:butterknife-compiler:8.8.1'
// SearchableSpinner
implementation 'com.toptoche.searchablespinner: searchablespinnerlibrary:1.3. 1'
// ViewPagerIndicator used for the display upon initial install
implementation 'com.github.JakeWharton:ViewPagerIndicator:2.4.1'
// Firebase UI
implementation 'com.firebaseui:firebase-ui-storage:2.1.0'
implementation 'com.firebaseui:firebase-ui-auth:2.1.0'
// Hive ProgressView
implementation 'com.github.zjywill:OverwatchProgress:1.4'
// Google Services
implementation 'com.google.android.gms:play-services-auth:12.0.0'
implementation 'com.google.android.gms:play-services-maps:12.0.0'
implementation 'com.google.android.gms:play-services-location:12.0.0'
// Gson
implementation 'com.google.code.gson:gson:2.8.5'
// Firebase Services
implementation 'com.google.firebase:firebase-auth:12.0.0'
implementation 'com.google.firebase:firebase-database:12.0.0'
implementation 'com.google.firebase:firebase-messaging:12.0.0'
implementation 'com.google.firebase:firebase-crash:12.0.0'
implementation 'com.google.firebase:firebase-analytics:12.0.0'
implementation 'com.google.firebase:firebase-storage:12.0.0'
implementation 'com.google.firebase:firebase-functions:12.0.0'
// CircleImageView
implementation 'de.hdodenhof:circleimageview:2.2.0'
// Easy Permissions
implementation 'pub.devrel:easypermissions:1.3.0'
// Rainbow SDK
implementation 'com.ale:rainbowsdk:1.40.0'
// Multidex
implementation 'com.android.support:multidex:1.0.3'
implementation 'com.android.support.constraint:constraint-layout: 1.1.2'
implementation 'com.android.support:design:27.1.1'
implementation 'com.android.support:animated-vector-drawable:27.1.1'
implementation 'com.android.support:support-vector-drawable:27.1.1'
implementation 'com.android.support:support-v4:27.1.1'
implementation 'com.android.support:cardview-v7:27.1.1'
implementation 'com.android.support:recyclerview-v7:27.1.1'
implementation 'com.android.support:appcompat-v7:27.1.1'
implementation 'com.android.support:customtabs:27.1.1'
implementation 'com.android.support:palette-v7:27.1.1'
// Crash Analytics
implementation('com.crashlytics.sdk.android: crashlytics:2.7.1@aar') {
transitive = true
}
-
Commentaire officiel
Hi,
Look at Build Release Error in Android SDK for a working solution.
Actions pour les commentaires -
Yes, the API SDK is still on version 1.40. My production app has SDK Version Target of 27, tested on devices with level 24 API (Xiaomi Redmi Note 4X, real device) and level 26 API (Nexus Emulator). Nothing wrong on Sandbox version. And yes, I only used those devices. Made another new project, and targeted SDK Version of 28, even copy pasted all of the dependencies from my app with the problem, including the Activity and methods, and it worked. I still have no idea until now, where did I do wrong.
-
I really don't know.
I was told it may be a problem with the "native Android json parser". But as/if you tested the sandbox and prod version on the same device the problem is elsewhere.For info, "isInDefaultCompany" is a boolean sent by Rainbow in login reply and not a string...
For the version 1.46, there will be a test for this.
Vous devez vous connecter pour laisser un commentaire.
Commentaires
6 commentaires