Open jimmyff opened 1 year ago
@jimmyff since the facebook native sdk 14.x the client token
must be added in your AndroidManifest.xml
and the next code is not needed any more
<activity android:name="com.facebook.FacebookActivity" android:configChanges="keyboard|keyboardHidden|screenLayout|screenSize|orientation" android:label="@string/app_name" />
<activity android:name="com.facebook.CustomTabActivity" android:exported="true">
<intent-filter>
<action android:name="android.intent.action.VIEW" />
<category android:name="android.intent.category.DEFAULT" />
<category android:name="android.intent.category.BROWSABLE" />
<data android:scheme="@string/fb_login_protocol_scheme" />
</intent-filter>
</activity>
Hey @darwin-morocho thanks for the reply. I will remove the code block you suggested, do you think that was causing all the crashes though?
I already include the client token:
<meta-data android:name="com.facebook.sdk.ApplicationId" android:value="@string/facebook_app_id" />
<meta-data android:name="com.facebook.sdk.ClientToken" android:value="@string/facebook_client_token" />
`also you have this line duplicated
<meta-data android:name="com.facebook.sdk.ApplicationId" android:value="@string/facebook_app_id" />
`also you have this line duplicated <meta-data android:name="com.facebook.sdk.ApplicationId" android:value="@string/facebook_app_id" />
`also you have this line duplicated
Yes thanks, I removed that on too. I just am unsure if these changes will fix the Resources$NotFoundException
crash
Yes thanks, I removed that on too. I just am unsure if these changes will fix the
Resources$NotFoundException
crash
The only way is running your project to be sure that the error has been gone
Will do a release today and report back
@darwin-morocho I'm still getting crash reports from FacebookActivity after removing the unnecessary AndroidManifest config. Do you have any other suggestions?
@darwin-morocho I'm still getting crash reports from FacebookActivity after removing the unnecessary AndroidManifest config. Do you have any other suggestions?
Try with the lastest version of this plugin. Also In your android/build.gradle check that you are not using jcenter instead mavenCentral. Check the example project
Still not managed to get to the bottom of this, however I keep seeing this in logcat, mentioning ZygoteInit
which is the same as the crashalytics error as they use facebook sign in:
2022-11-14 16:34:30.288 3795-3795/? W/Resources: Drawable com.android.systemui:drawable/subroom_active_background has unresolved theme attributes! Consider using Resources.getDrawable(int, Theme) or Context.getDrawable(int).
java.lang.RuntimeException
at android.content.res.Resources.getDrawable(Resources.java:964)
at com.android.systemui.qp.SubroomWifiSettingsView.updateView(SubroomWifiSettingsView.java:92)
at com.android.systemui.qp.SubscreenWifiController$WifiSignalCallback.setWifiIndicators(SubscreenWifiController.java:144)
at com.android.systemui.statusbar.policy.CallbackHandler.lambda$setWifiIndicators$0(CallbackHandler.java:134)
at com.android.systemui.statusbar.policy.CallbackHandler.$r8$lambda$eo_aw2C3NKZ3xoTafvO2sST_bIs(Unknown Source:0)
at com.android.systemui.statusbar.policy.CallbackHandler$$ExternalSyntheticLambda4.run(Unknown Source:4)
at android.os.Handler.handleCallback(Handler.java:938)
at android.os.Handler.dispatchMessage(Handler.java:99)
at android.os.Looper.loopOnce(Looper.java:226)
at android.os.Looper.loop(Looper.java:313)
at android.app.ActivityThread.main(ActivityThread.java:8855)
at java.lang.reflect.Method.invoke(Native Method)
at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:571)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1135)
Looks like this: https://stackoverflow.com/a/30267048/13051067
What version are you using?
4.4.0+1
What OS and version are you using to local deploy your application?
MacOS 12.4
What platforms are you seeing the problem on?
Android
pubspec.yaml
Describe the Bug
Getting numerous crash repots via Crashalytics on Android production:
I've been struggling to track down where this is coming from, however looking at the logs- the last screen before the crash is always FacebookActivity:
Could it be looking for an icon/logo that doesn't exist in my app and thats causing the crash?
Expected Behavior
No crashes
To Reproduce
Hard to say
Relevant log output
No response
flutter doctor -v
Info.plist (iOS)
No response
Podfile (iOS)
No response
AndroidManifest.xml
MainActivity.java
No response
MainActivity.kt
No response
index.html
No response
Info.plist (macOS)
No response