How to solve app launch - app is stuck on white screen
Clash Royale CLAN TAG#URR8PPP
up vote
19
down vote
favorite
I check the error log, and it shows:
08-31 13:36:18.778 13207-13207/? I/art: Late-enabling -Xcheck:jni
08-31 13:36:18.877 13207-13207/com.knowyourmeds D/FirebaseApp: com.google.firebase.auth.FirebaseAuth is not linked. Skipping initialization.
08-31 13:36:18.888 13207-13207/com.knowyourmeds D/FirebaseApp: com.google.firebase.crash.FirebaseCrash is not linked. Skipping initialization.
08-31 13:36:18.902 13207-13207/com.knowyourmeds V/FA: Cancelling job. JobID: 380685678
08-31 13:36:18.904 13207-13207/com.knowyourmeds V/FA: Registered activity lifecycle callback
08-31 13:36:18.905 13207-13207/com.knowyourmeds I/FirebaseInitProvider: FirebaseApp initialization successful
08-31 13:36:18.937 13207-13224/com.knowyourmeds V/FA: Collection enabled
08-31 13:36:18.938 13207-13224/com.knowyourmeds V/FA: App package, google app id: com.knowyourmeds, 1:694023459332:android:ffd849037d9dc14b
08-31 13:36:18.939 13207-13224/com.knowyourmeds I/FA: App measurement is starting up, version: 11910
To enable debug logging run: adb shell setprop log.tag.FA VERBOSE
To enable faster debug mode event logging run:
adb shell setprop debug.firebase.analytics.app com.knowyourmeds
08-31 13:36:18.939 13207-13224/com.knowyourmeds D/FA: Debug-level message logging enabled
08-31 13:36:18.956 13207-13224/com.knowyourmeds V/FA: Connecting to remote service
08-31 13:36:18.980 13207-13207/com.knowyourmeds I/CrashlyticsCore: Initializing Crashlytics 2.6.1.23
08-31 13:36:18.999 13207-13224/com.knowyourmeds V/FA: Connection attempt already in progress
08-31 13:36:19.008 13207-13207/com.knowyourmeds I/CrashlyticsInitProvider: CrashlyticsInitProvider initialization successful
08-31 13:36:19.018 13207-13207/com.knowyourmeds E/com.facebook.internal.AttributionIdentifiers: getAttributionIdentifiers should not be called from the main thread
08-31 13:36:19.025 13207-13243/com.knowyourmeds D/NetworkSecurityConfig: No Network Security Config specified, using platform default
08-31 13:36:48.923 13207-13223/com.knowyourmeds E/FirebaseInstanceId: Token retrieval failed: SERVICE_NOT_AVAILABLE
I also tried cleaning the project, restarting Android Studio and deleted the app from the device.
How should I resolve this issue?
android
add a comment |Â
up vote
19
down vote
favorite
I check the error log, and it shows:
08-31 13:36:18.778 13207-13207/? I/art: Late-enabling -Xcheck:jni
08-31 13:36:18.877 13207-13207/com.knowyourmeds D/FirebaseApp: com.google.firebase.auth.FirebaseAuth is not linked. Skipping initialization.
08-31 13:36:18.888 13207-13207/com.knowyourmeds D/FirebaseApp: com.google.firebase.crash.FirebaseCrash is not linked. Skipping initialization.
08-31 13:36:18.902 13207-13207/com.knowyourmeds V/FA: Cancelling job. JobID: 380685678
08-31 13:36:18.904 13207-13207/com.knowyourmeds V/FA: Registered activity lifecycle callback
08-31 13:36:18.905 13207-13207/com.knowyourmeds I/FirebaseInitProvider: FirebaseApp initialization successful
08-31 13:36:18.937 13207-13224/com.knowyourmeds V/FA: Collection enabled
08-31 13:36:18.938 13207-13224/com.knowyourmeds V/FA: App package, google app id: com.knowyourmeds, 1:694023459332:android:ffd849037d9dc14b
08-31 13:36:18.939 13207-13224/com.knowyourmeds I/FA: App measurement is starting up, version: 11910
To enable debug logging run: adb shell setprop log.tag.FA VERBOSE
To enable faster debug mode event logging run:
adb shell setprop debug.firebase.analytics.app com.knowyourmeds
08-31 13:36:18.939 13207-13224/com.knowyourmeds D/FA: Debug-level message logging enabled
08-31 13:36:18.956 13207-13224/com.knowyourmeds V/FA: Connecting to remote service
08-31 13:36:18.980 13207-13207/com.knowyourmeds I/CrashlyticsCore: Initializing Crashlytics 2.6.1.23
08-31 13:36:18.999 13207-13224/com.knowyourmeds V/FA: Connection attempt already in progress
08-31 13:36:19.008 13207-13207/com.knowyourmeds I/CrashlyticsInitProvider: CrashlyticsInitProvider initialization successful
08-31 13:36:19.018 13207-13207/com.knowyourmeds E/com.facebook.internal.AttributionIdentifiers: getAttributionIdentifiers should not be called from the main thread
08-31 13:36:19.025 13207-13243/com.knowyourmeds D/NetworkSecurityConfig: No Network Security Config specified, using platform default
08-31 13:36:48.923 13207-13223/com.knowyourmeds E/FirebaseInstanceId: Token retrieval failed: SERVICE_NOT_AVAILABLE
I also tried cleaning the project, restarting Android Studio and deleted the app from the device.
How should I resolve this issue?
android
add a comment |Â
up vote
19
down vote
favorite
up vote
19
down vote
favorite
I check the error log, and it shows:
08-31 13:36:18.778 13207-13207/? I/art: Late-enabling -Xcheck:jni
08-31 13:36:18.877 13207-13207/com.knowyourmeds D/FirebaseApp: com.google.firebase.auth.FirebaseAuth is not linked. Skipping initialization.
08-31 13:36:18.888 13207-13207/com.knowyourmeds D/FirebaseApp: com.google.firebase.crash.FirebaseCrash is not linked. Skipping initialization.
08-31 13:36:18.902 13207-13207/com.knowyourmeds V/FA: Cancelling job. JobID: 380685678
08-31 13:36:18.904 13207-13207/com.knowyourmeds V/FA: Registered activity lifecycle callback
08-31 13:36:18.905 13207-13207/com.knowyourmeds I/FirebaseInitProvider: FirebaseApp initialization successful
08-31 13:36:18.937 13207-13224/com.knowyourmeds V/FA: Collection enabled
08-31 13:36:18.938 13207-13224/com.knowyourmeds V/FA: App package, google app id: com.knowyourmeds, 1:694023459332:android:ffd849037d9dc14b
08-31 13:36:18.939 13207-13224/com.knowyourmeds I/FA: App measurement is starting up, version: 11910
To enable debug logging run: adb shell setprop log.tag.FA VERBOSE
To enable faster debug mode event logging run:
adb shell setprop debug.firebase.analytics.app com.knowyourmeds
08-31 13:36:18.939 13207-13224/com.knowyourmeds D/FA: Debug-level message logging enabled
08-31 13:36:18.956 13207-13224/com.knowyourmeds V/FA: Connecting to remote service
08-31 13:36:18.980 13207-13207/com.knowyourmeds I/CrashlyticsCore: Initializing Crashlytics 2.6.1.23
08-31 13:36:18.999 13207-13224/com.knowyourmeds V/FA: Connection attempt already in progress
08-31 13:36:19.008 13207-13207/com.knowyourmeds I/CrashlyticsInitProvider: CrashlyticsInitProvider initialization successful
08-31 13:36:19.018 13207-13207/com.knowyourmeds E/com.facebook.internal.AttributionIdentifiers: getAttributionIdentifiers should not be called from the main thread
08-31 13:36:19.025 13207-13243/com.knowyourmeds D/NetworkSecurityConfig: No Network Security Config specified, using platform default
08-31 13:36:48.923 13207-13223/com.knowyourmeds E/FirebaseInstanceId: Token retrieval failed: SERVICE_NOT_AVAILABLE
I also tried cleaning the project, restarting Android Studio and deleted the app from the device.
How should I resolve this issue?
android
I check the error log, and it shows:
08-31 13:36:18.778 13207-13207/? I/art: Late-enabling -Xcheck:jni
08-31 13:36:18.877 13207-13207/com.knowyourmeds D/FirebaseApp: com.google.firebase.auth.FirebaseAuth is not linked. Skipping initialization.
08-31 13:36:18.888 13207-13207/com.knowyourmeds D/FirebaseApp: com.google.firebase.crash.FirebaseCrash is not linked. Skipping initialization.
08-31 13:36:18.902 13207-13207/com.knowyourmeds V/FA: Cancelling job. JobID: 380685678
08-31 13:36:18.904 13207-13207/com.knowyourmeds V/FA: Registered activity lifecycle callback
08-31 13:36:18.905 13207-13207/com.knowyourmeds I/FirebaseInitProvider: FirebaseApp initialization successful
08-31 13:36:18.937 13207-13224/com.knowyourmeds V/FA: Collection enabled
08-31 13:36:18.938 13207-13224/com.knowyourmeds V/FA: App package, google app id: com.knowyourmeds, 1:694023459332:android:ffd849037d9dc14b
08-31 13:36:18.939 13207-13224/com.knowyourmeds I/FA: App measurement is starting up, version: 11910
To enable debug logging run: adb shell setprop log.tag.FA VERBOSE
To enable faster debug mode event logging run:
adb shell setprop debug.firebase.analytics.app com.knowyourmeds
08-31 13:36:18.939 13207-13224/com.knowyourmeds D/FA: Debug-level message logging enabled
08-31 13:36:18.956 13207-13224/com.knowyourmeds V/FA: Connecting to remote service
08-31 13:36:18.980 13207-13207/com.knowyourmeds I/CrashlyticsCore: Initializing Crashlytics 2.6.1.23
08-31 13:36:18.999 13207-13224/com.knowyourmeds V/FA: Connection attempt already in progress
08-31 13:36:19.008 13207-13207/com.knowyourmeds I/CrashlyticsInitProvider: CrashlyticsInitProvider initialization successful
08-31 13:36:19.018 13207-13207/com.knowyourmeds E/com.facebook.internal.AttributionIdentifiers: getAttributionIdentifiers should not be called from the main thread
08-31 13:36:19.025 13207-13243/com.knowyourmeds D/NetworkSecurityConfig: No Network Security Config specified, using platform default
08-31 13:36:48.923 13207-13223/com.knowyourmeds E/FirebaseInstanceId: Token retrieval failed: SERVICE_NOT_AVAILABLE
I also tried cleaning the project, restarting Android Studio and deleted the app from the device.
How should I resolve this issue?
android
android
edited Aug 31 at 13:49
Peter Mortensen
13k1983111
13k1983111
asked Aug 31 at 8:19
Harsh Shah
434418
434418
add a comment |Â
add a comment |Â
6 Answers
6
active
oldest
votes
up vote
7
down vote
accepted
Try below:
1. In your app level gradle, you must have used implementation "com.facebook.android:facebook-android-sdk:[4,5)"
2. Try to remove this or upgrade to the latest sdk
1
removed that line solved my problem
â Harsh Shah
Aug 31 at 11:29
stop abusing rollbacks
â Samuel Liewâ¦
Sep 7 at 22:07
add a comment |Â
up vote
25
down vote
I just fixed the issue. The reason for this issue is you use 'com.facebook.android:facebook-android-sdk:4.+', Facebook auto update and have an error inside the SDK. Changing the version can fix the problem.
Use:
com.facebook.android:facebook-android-sdk:4.35.0
This issues also happened in react-native-fbsdk. I have to do the same thing as above.
â siripan
Sep 4 at 7:58
Man, you guys helped me to sort out.. A big thanks from me and my company to all of you .. (y)
â Aveek
Sep 14 at 2:36
add a comment |Â
up vote
18
down vote
It seems like some facebook SDK error. I got the same today and solved it by replacing dynamic version in the gradle file to the stable.
Replace this:
implementation "com.facebook.android:facebook-android-sdk:[4,5)"
to this:
implementation "com.facebook.android:facebook-android-sdk:4.35.0"
4.35.0 is the stable version of the SDK from facebook GitHub https://github.com/facebook/facebook-android-sdk
add a comment |Â
up vote
3
down vote
Just revert the FacebookSDK back to 4.35.0. The version 4.36.0 causes the stuck in main thread.
E/com.facebook.internal.AttributionIdentifiers: getAttributionIdentifiers should not be called from the main thread
add a comment |Â
up vote
1
down vote
I think you should look closely at this line:
08-31 13:36:19.018 13207-13207/com.knowyourmeds E/com.facebook.internal.AttributionIdentifiers: getAttributionIdentifiers should not be called from the main thread
I think you should try to create an AsyncTask to call this method, as well as any other call requiring heavy processing (network, computation, ...).
Currently your UI is waiting for all the processing to finish before drawing.
This comes from speculations, it depends on your code organization, but that's the most plausible explanation.
Experienced this also this afternoon. App was working fine this morning. Reverted all my changes but error still exists. I also tried removing all facebook sdk functionalities in my app and just retained the import in the app build.gradle. Still experiencing the stuck on white screen problem. Please help.
â Rio Marie A. Callos
Aug 31 at 10:03
add a comment |Â
up vote
1
down vote
I had same problem this library worked for me because this is facebook
stable version.
compile 'com.facebook.android:facebook-android-sdk:4.35.0'
add a comment |Â
6 Answers
6
active
oldest
votes
6 Answers
6
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
7
down vote
accepted
Try below:
1. In your app level gradle, you must have used implementation "com.facebook.android:facebook-android-sdk:[4,5)"
2. Try to remove this or upgrade to the latest sdk
1
removed that line solved my problem
â Harsh Shah
Aug 31 at 11:29
stop abusing rollbacks
â Samuel Liewâ¦
Sep 7 at 22:07
add a comment |Â
up vote
7
down vote
accepted
Try below:
1. In your app level gradle, you must have used implementation "com.facebook.android:facebook-android-sdk:[4,5)"
2. Try to remove this or upgrade to the latest sdk
1
removed that line solved my problem
â Harsh Shah
Aug 31 at 11:29
stop abusing rollbacks
â Samuel Liewâ¦
Sep 7 at 22:07
add a comment |Â
up vote
7
down vote
accepted
up vote
7
down vote
accepted
Try below:
1. In your app level gradle, you must have used implementation "com.facebook.android:facebook-android-sdk:[4,5)"
2. Try to remove this or upgrade to the latest sdk
Try below:
1. In your app level gradle, you must have used implementation "com.facebook.android:facebook-android-sdk:[4,5)"
2. Try to remove this or upgrade to the latest sdk
edited Sep 7 at 9:09
answered Aug 31 at 11:28
Sahil Bhavsar
956
956
1
removed that line solved my problem
â Harsh Shah
Aug 31 at 11:29
stop abusing rollbacks
â Samuel Liewâ¦
Sep 7 at 22:07
add a comment |Â
1
removed that line solved my problem
â Harsh Shah
Aug 31 at 11:29
stop abusing rollbacks
â Samuel Liewâ¦
Sep 7 at 22:07
1
1
removed that line solved my problem
â Harsh Shah
Aug 31 at 11:29
removed that line solved my problem
â Harsh Shah
Aug 31 at 11:29
stop abusing rollbacks
â Samuel Liewâ¦
Sep 7 at 22:07
stop abusing rollbacks
â Samuel Liewâ¦
Sep 7 at 22:07
add a comment |Â
up vote
25
down vote
I just fixed the issue. The reason for this issue is you use 'com.facebook.android:facebook-android-sdk:4.+', Facebook auto update and have an error inside the SDK. Changing the version can fix the problem.
Use:
com.facebook.android:facebook-android-sdk:4.35.0
This issues also happened in react-native-fbsdk. I have to do the same thing as above.
â siripan
Sep 4 at 7:58
Man, you guys helped me to sort out.. A big thanks from me and my company to all of you .. (y)
â Aveek
Sep 14 at 2:36
add a comment |Â
up vote
25
down vote
I just fixed the issue. The reason for this issue is you use 'com.facebook.android:facebook-android-sdk:4.+', Facebook auto update and have an error inside the SDK. Changing the version can fix the problem.
Use:
com.facebook.android:facebook-android-sdk:4.35.0
This issues also happened in react-native-fbsdk. I have to do the same thing as above.
â siripan
Sep 4 at 7:58
Man, you guys helped me to sort out.. A big thanks from me and my company to all of you .. (y)
â Aveek
Sep 14 at 2:36
add a comment |Â
up vote
25
down vote
up vote
25
down vote
I just fixed the issue. The reason for this issue is you use 'com.facebook.android:facebook-android-sdk:4.+', Facebook auto update and have an error inside the SDK. Changing the version can fix the problem.
Use:
com.facebook.android:facebook-android-sdk:4.35.0
I just fixed the issue. The reason for this issue is you use 'com.facebook.android:facebook-android-sdk:4.+', Facebook auto update and have an error inside the SDK. Changing the version can fix the problem.
Use:
com.facebook.android:facebook-android-sdk:4.35.0
edited Aug 31 at 14:37
Peter Mortensen
13k1983111
13k1983111
answered Aug 31 at 10:27
Always Wei
26124
26124
This issues also happened in react-native-fbsdk. I have to do the same thing as above.
â siripan
Sep 4 at 7:58
Man, you guys helped me to sort out.. A big thanks from me and my company to all of you .. (y)
â Aveek
Sep 14 at 2:36
add a comment |Â
This issues also happened in react-native-fbsdk. I have to do the same thing as above.
â siripan
Sep 4 at 7:58
Man, you guys helped me to sort out.. A big thanks from me and my company to all of you .. (y)
â Aveek
Sep 14 at 2:36
This issues also happened in react-native-fbsdk. I have to do the same thing as above.
â siripan
Sep 4 at 7:58
This issues also happened in react-native-fbsdk. I have to do the same thing as above.
â siripan
Sep 4 at 7:58
Man, you guys helped me to sort out.. A big thanks from me and my company to all of you .. (y)
â Aveek
Sep 14 at 2:36
Man, you guys helped me to sort out.. A big thanks from me and my company to all of you .. (y)
â Aveek
Sep 14 at 2:36
add a comment |Â
up vote
18
down vote
It seems like some facebook SDK error. I got the same today and solved it by replacing dynamic version in the gradle file to the stable.
Replace this:
implementation "com.facebook.android:facebook-android-sdk:[4,5)"
to this:
implementation "com.facebook.android:facebook-android-sdk:4.35.0"
4.35.0 is the stable version of the SDK from facebook GitHub https://github.com/facebook/facebook-android-sdk
add a comment |Â
up vote
18
down vote
It seems like some facebook SDK error. I got the same today and solved it by replacing dynamic version in the gradle file to the stable.
Replace this:
implementation "com.facebook.android:facebook-android-sdk:[4,5)"
to this:
implementation "com.facebook.android:facebook-android-sdk:4.35.0"
4.35.0 is the stable version of the SDK from facebook GitHub https://github.com/facebook/facebook-android-sdk
add a comment |Â
up vote
18
down vote
up vote
18
down vote
It seems like some facebook SDK error. I got the same today and solved it by replacing dynamic version in the gradle file to the stable.
Replace this:
implementation "com.facebook.android:facebook-android-sdk:[4,5)"
to this:
implementation "com.facebook.android:facebook-android-sdk:4.35.0"
4.35.0 is the stable version of the SDK from facebook GitHub https://github.com/facebook/facebook-android-sdk
It seems like some facebook SDK error. I got the same today and solved it by replacing dynamic version in the gradle file to the stable.
Replace this:
implementation "com.facebook.android:facebook-android-sdk:[4,5)"
to this:
implementation "com.facebook.android:facebook-android-sdk:4.35.0"
4.35.0 is the stable version of the SDK from facebook GitHub https://github.com/facebook/facebook-android-sdk
edited Aug 31 at 14:48
answered Aug 31 at 10:22
dantes_21
29516
29516
add a comment |Â
add a comment |Â
up vote
3
down vote
Just revert the FacebookSDK back to 4.35.0. The version 4.36.0 causes the stuck in main thread.
E/com.facebook.internal.AttributionIdentifiers: getAttributionIdentifiers should not be called from the main thread
add a comment |Â
up vote
3
down vote
Just revert the FacebookSDK back to 4.35.0. The version 4.36.0 causes the stuck in main thread.
E/com.facebook.internal.AttributionIdentifiers: getAttributionIdentifiers should not be called from the main thread
add a comment |Â
up vote
3
down vote
up vote
3
down vote
Just revert the FacebookSDK back to 4.35.0. The version 4.36.0 causes the stuck in main thread.
E/com.facebook.internal.AttributionIdentifiers: getAttributionIdentifiers should not be called from the main thread
Just revert the FacebookSDK back to 4.35.0. The version 4.36.0 causes the stuck in main thread.
E/com.facebook.internal.AttributionIdentifiers: getAttributionIdentifiers should not be called from the main thread
answered Aug 31 at 15:25
VÃÂn Trần
3111
3111
add a comment |Â
add a comment |Â
up vote
1
down vote
I think you should look closely at this line:
08-31 13:36:19.018 13207-13207/com.knowyourmeds E/com.facebook.internal.AttributionIdentifiers: getAttributionIdentifiers should not be called from the main thread
I think you should try to create an AsyncTask to call this method, as well as any other call requiring heavy processing (network, computation, ...).
Currently your UI is waiting for all the processing to finish before drawing.
This comes from speculations, it depends on your code organization, but that's the most plausible explanation.
Experienced this also this afternoon. App was working fine this morning. Reverted all my changes but error still exists. I also tried removing all facebook sdk functionalities in my app and just retained the import in the app build.gradle. Still experiencing the stuck on white screen problem. Please help.
â Rio Marie A. Callos
Aug 31 at 10:03
add a comment |Â
up vote
1
down vote
I think you should look closely at this line:
08-31 13:36:19.018 13207-13207/com.knowyourmeds E/com.facebook.internal.AttributionIdentifiers: getAttributionIdentifiers should not be called from the main thread
I think you should try to create an AsyncTask to call this method, as well as any other call requiring heavy processing (network, computation, ...).
Currently your UI is waiting for all the processing to finish before drawing.
This comes from speculations, it depends on your code organization, but that's the most plausible explanation.
Experienced this also this afternoon. App was working fine this morning. Reverted all my changes but error still exists. I also tried removing all facebook sdk functionalities in my app and just retained the import in the app build.gradle. Still experiencing the stuck on white screen problem. Please help.
â Rio Marie A. Callos
Aug 31 at 10:03
add a comment |Â
up vote
1
down vote
up vote
1
down vote
I think you should look closely at this line:
08-31 13:36:19.018 13207-13207/com.knowyourmeds E/com.facebook.internal.AttributionIdentifiers: getAttributionIdentifiers should not be called from the main thread
I think you should try to create an AsyncTask to call this method, as well as any other call requiring heavy processing (network, computation, ...).
Currently your UI is waiting for all the processing to finish before drawing.
This comes from speculations, it depends on your code organization, but that's the most plausible explanation.
I think you should look closely at this line:
08-31 13:36:19.018 13207-13207/com.knowyourmeds E/com.facebook.internal.AttributionIdentifiers: getAttributionIdentifiers should not be called from the main thread
I think you should try to create an AsyncTask to call this method, as well as any other call requiring heavy processing (network, computation, ...).
Currently your UI is waiting for all the processing to finish before drawing.
This comes from speculations, it depends on your code organization, but that's the most plausible explanation.
answered Aug 31 at 8:35
Antoine
779622
779622
Experienced this also this afternoon. App was working fine this morning. Reverted all my changes but error still exists. I also tried removing all facebook sdk functionalities in my app and just retained the import in the app build.gradle. Still experiencing the stuck on white screen problem. Please help.
â Rio Marie A. Callos
Aug 31 at 10:03
add a comment |Â
Experienced this also this afternoon. App was working fine this morning. Reverted all my changes but error still exists. I also tried removing all facebook sdk functionalities in my app and just retained the import in the app build.gradle. Still experiencing the stuck on white screen problem. Please help.
â Rio Marie A. Callos
Aug 31 at 10:03
Experienced this also this afternoon. App was working fine this morning. Reverted all my changes but error still exists. I also tried removing all facebook sdk functionalities in my app and just retained the import in the app build.gradle. Still experiencing the stuck on white screen problem. Please help.
â Rio Marie A. Callos
Aug 31 at 10:03
Experienced this also this afternoon. App was working fine this morning. Reverted all my changes but error still exists. I also tried removing all facebook sdk functionalities in my app and just retained the import in the app build.gradle. Still experiencing the stuck on white screen problem. Please help.
â Rio Marie A. Callos
Aug 31 at 10:03
add a comment |Â
up vote
1
down vote
I had same problem this library worked for me because this is facebook
stable version.
compile 'com.facebook.android:facebook-android-sdk:4.35.0'
add a comment |Â
up vote
1
down vote
I had same problem this library worked for me because this is facebook
stable version.
compile 'com.facebook.android:facebook-android-sdk:4.35.0'
add a comment |Â
up vote
1
down vote
up vote
1
down vote
I had same problem this library worked for me because this is facebook
stable version.
compile 'com.facebook.android:facebook-android-sdk:4.35.0'
I had same problem this library worked for me because this is facebook
stable version.
compile 'com.facebook.android:facebook-android-sdk:4.35.0'
answered Sep 14 at 4:42
Abdul Basit Rishi
196
196
add a comment |Â
add a comment |Â
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f52111298%2fhow-to-solve-app-launch-app-is-stuck-on-white-screen%23new-answer', 'question_page');
);
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password