Jump to content

emby crash


Recommended Posts

Posted
C:\Users\windows\Downloads\Compressed\Tiny-Fastboot-Script_v1.10.5_zh-CN_by_AlphaEva>adb logcat -s AndroidRuntime
--------- beginning of crash
12-11 22:38:18.006  7443  7591 E AndroidRuntime: FATAL EXCEPTION: GoogleApiHandler
12-11 22:38:18.006  7443  7591 E AndroidRuntime: Process: com.mb.android, PID: 7443
12-11 22:38:18.006  7443  7591 E AndroidRuntime: java.lang.IllegalArgumentException: com.mb.android: Targeting U+ (version 34 and above) disallows creating or retrieving a PendingIntent with FLAG_MUTABLE, an implicit Intent within and without FLAG_NO_CREATE and FLAG_ALLOW_UNSAFE_IMPLICIT_INTENT for security reasons. To retrieve an already existing PendingIntent, use FLAG_NO_CREATE, however, to create a new PendingIntent with an implicit Intent use FLAG_IMMUTABLE.
12-11 22:38:18.006  7443  7591 E AndroidRuntime:        at android.os.Parcel.createExceptionOrNull(Parcel.java:3061)
12-11 22:38:18.006  7443  7591 E AndroidRuntime:        at android.os.Parcel.createException(Parcel.java:3041)
12-11 22:38:18.006  7443  7591 E AndroidRuntime:        at android.os.Parcel.readException(Parcel.java:3024)
12-11 22:38:18.006  7443  7591 E AndroidRuntime:        at android.os.Parcel.readException(Parcel.java:2966)
12-11 22:38:18.006  7443  7591 E AndroidRuntime:        at android.app.IActivityManager$Stub$Proxy.getIntentSenderWithFeature(IActivityManager.java:6962)
12-11 22:38:18.006  7443  7591 E AndroidRuntime:        at android.app.PendingIntent.getActivityAsUser(PendingIntent.java:554)
12-11 22:38:18.006  7443  7591 E AndroidRuntime:        at android.app.PendingIntent.getActivity(PendingIntent.java:535)
12-11 22:38:18.006  7443  7591 E AndroidRuntime:        at android.app.PendingIntent.getActivity(PendingIntent.java:499)
12-11 22:38:18.006  7443  7591 E AndroidRuntime:        at com.google.android.gms.internal.common.zzd.zza(com.google.android.gms:play-services-basement@@18.0.0:1)
12-11 22:38:18.006  7443  7591 E AndroidRuntime:        at com.google.android.gms.common.GoogleApiAvailabilityLight.getErrorResolutionPendingIntent(com.google.android.gms:play-services-basement@@18.0.0:3)
12-11 22:38:18.006  7443  7591 E AndroidRuntime:        at com.google.android.gms.common.GoogleApiAvailabilityLight.getErrorResolutionPendingIntent(com.google.android.gms:play-services-basement@@18.0.0:1)
12-11 22:38:18.006  7443  7591 E AndroidRuntime:        at com.google.android.gms.common.GoogleApiAvailability.getErrorResolutionPendingIntent(com.google.android.gms:play-services-base@@18.0.1:1)
12-11 22:38:18.006  7443  7591 E AndroidRuntime:        at com.google.android.gms.common.GoogleApiAvailability.getErrorResolutionPendingIntent(com.google.android.gms:play-services-base@@18.0.1:4)
12-11 22:38:18.006  7443  7591 E AndroidRuntime:        at com.google.android.gms.common.GoogleApiAvailability.zah(com.google.android.gms:play-services-base@@18.0.1:2)
12-11 22:38:18.006  7443  7591 E AndroidRuntime:        at com.google.android.gms.common.api.internal.GoogleApiManager.zaG(com.google.android.gms:play-services-base@@18.0.1:1)
12-11 22:38:18.006  7443  7591 E AndroidRuntime:        at com.google.android.gms.common.api.internal.zabq.zar(com.google.android.gms:play-services-base@@18.0.1:21)
12-11 22:38:18.006  7443  7591 E AndroidRuntime:        at com.google.android.gms.common.api.internal.zabq.zao(com.google.android.gms:play-services-base@@18.0.1:13)
12-11 22:38:18.006  7443  7591 E AndroidRuntime:        at com.google.android.gms.common.api.internal.zabq.zap(com.google.android.gms:play-services-base@@18.0.1:8)
12-11 22:38:18.006  7443  7591 E AndroidRuntime:        at com.google.android.gms.common.api.internal.GoogleApiManager.handleMessage(com.google.android.gms:play-services-base@@18.0.1:64)
12-11 22:38:18.006  7443  7591 E AndroidRuntime:        at android.os.Handler.dispatchMessage(Handler.java:107)
12-11 22:38:18.006  7443  7591 E AndroidRuntime:        at android.os.Looper.loopOnce(Looper.java:242)
12-11 22:38:18.006  7443  7591 E AndroidRuntime:        at android.os.Looper.loop(Looper.java:362)
12-11 22:38:18.006  7443  7591 E AndroidRuntime:        at android.os.HandlerThread.run(HandlerThread.java:85)
12-11 22:38:18.006  7443  7591 E AndroidRuntime: Caused by: android.os.RemoteException: Remote stack trace:
12-11 22:38:18.006  7443  7591 E AndroidRuntime:        at com.android.server.am.ActivityManagerService.getIntentSenderWithFeatureAsApp(ActivityManagerService.java:5561)
12-11 22:38:18.006  7443  7591 E AndroidRuntime:        at com.android.server.am.ActivityManagerService.getIntentSenderWithFeature(ActivityManagerService.java:5504)
12-11 22:38:18.006  7443  7591 E AndroidRuntime:        at android.app.IActivityManager$Stub.onTransact$getIntentSenderWithFeature$(IActivityManager.java:11471)
12-11 22:38:18.006  7443  7591 E AndroidRuntime:        at android.app.IActivityManager$Stub.onTransact(IActivityManager.java:3380)
12-11 22:38:18.006  7443  7591 E AndroidRuntime:        at com.android.server.am.ActivityManagerService.onTransact(ActivityManagerService.java:2847)


Just installed the Emzy app Moto s50neo on Android 14 and it crash

 

Posted

Hi, is that all of the logcat output that you have for it?

Posted
23 hours ago, Luke said:

Hi, is that all of the logcat output that you have for it?

I don't know the corresponding emby logcat tag. However, based on my experience in Android development, these logs are already sufficient

Posted

What version number of the Emby android app is this?

Posted
On 12/13/2024 at 1:59 AM, Luke said:

What version number of the Emby android app is this?

3.4.27

Posted

Can you try updating to 3.4.28 and see how things compare? Thanks !

Posted
2 hours ago, Luke said:

Can you try updating to 3.4.28 and see how things compare? Thanks !

Still reporting errors

 

12-17 09:49:40.837 10092 10184 E AndroidRuntime: FATAL EXCEPTION: GoogleApiHandler
12-17 09:49:40.837 10092 10184 E AndroidRuntime: Process: com.mb.android, PID: 10092
12-17 09:49:40.837 10092 10184 E AndroidRuntime: java.lang.IllegalArgumentException: com.mb.android: Targeting U+ (version 34 and above) disallows creating or retrieving a PendingIntent with FLAG_MUTABLE, an implicit Intent within and without FLAG_NO_CREATE and FLAG_ALLOW_UNSAFE_IMPLICIT_INTENT for security reasons. To retrieve an already existing PendingIntent, use FLAG_NO_CREATE, however, to create a new PendingIntent with an implicit Intent use FLAG_IMMUTABLE.
12-17 09:49:40.837 10092 10184 E AndroidRuntime:        at android.os.Parcel.createExceptionOrNull(Parcel.java:3061)
12-17 09:49:40.837 10092 10184 E AndroidRuntime:        at android.os.Parcel.createException(Parcel.java:3041)
12-17 09:49:40.837 10092 10184 E AndroidRuntime:        at android.os.Parcel.readException(Parcel.java:3024)
12-17 09:49:40.837 10092 10184 E AndroidRuntime:        at android.os.Parcel.readException(Parcel.java:2966)
12-17 09:49:40.837 10092 10184 E AndroidRuntime:        at android.app.IActivityManager$Stub$Proxy.getIntentSenderWithFeature(IActivityManager.java:6962)
12-17 09:49:40.837 10092 10184 E AndroidRuntime:        at android.app.PendingIntent.getActivityAsUser(PendingIntent.java:554)
12-17 09:49:40.837 10092 10184 E AndroidRuntime:        at android.app.PendingIntent.getActivity(PendingIntent.java:535)
12-17 09:49:40.837 10092 10184 E AndroidRuntime:        at android.app.PendingIntent.getActivity(PendingIntent.java:499)
12-17 09:49:40.837 10092 10184 E AndroidRuntime:        at com.google.android.gms.internal.common.zzd.zza(com.google.android.gms:play-services-basement@@18.0.0:1)
12-17 09:49:40.837 10092 10184 E AndroidRuntime:        at com.google.android.gms.common.GoogleApiAvailabilityLight.getErrorResolutionPendingIntent(com.google.android.gms:play-services-basement@@18.0.0:3)
12-17 09:49:40.837 10092 10184 E AndroidRuntime:        at com.google.android.gms.common.GoogleApiAvailabilityLight.getErrorResolutionPendingIntent(com.google.android.gms:play-services-basement@@18.0.0:1)
12-17 09:49:40.837 10092 10184 E AndroidRuntime:        at com.google.android.gms.common.GoogleApiAvailability.getErrorResolutionPendingIntent(com.google.android.gms:play-services-base@@18.0.1:1)
12-17 09:49:40.837 10092 10184 E AndroidRuntime:        at com.google.android.gms.common.GoogleApiAvailability.getErrorResolutionPendingIntent(com.google.android.gms:play-services-base@@18.0.1:4)
12-17 09:49:40.837 10092 10184 E AndroidRuntime:        at com.google.android.gms.common.GoogleApiAvailability.zah(com.google.android.gms:play-services-base@@18.0.1:2)
12-17 09:49:40.837 10092 10184 E AndroidRuntime:        at com.google.android.gms.common.api.internal.GoogleApiManager.zaG(com.google.android.gms:play-services-base@@18.0.1:1)
12-17 09:49:40.837 10092 10184 E AndroidRuntime:        at com.google.android.gms.common.api.internal.zabq.zar(com.google.android.gms:play-services-base@@18.0.1:21)
12-17 09:49:40.837 10092 10184 E AndroidRuntime:        at com.google.android.gms.common.api.internal.zabq.zao(com.google.android.gms:play-services-base@@18.0.1:13)
12-17 09:49:40.837 10092 10184 E AndroidRuntime:        at com.google.android.gms.common.api.internal.zabq.zap(com.google.android.gms:play-services-base@@18.0.1:8)
12-17 09:49:40.837 10092 10184 E AndroidRuntime:        at com.google.android.gms.common.api.internal.GoogleApiManager.handleMessage(com.google.android.gms:play-services-base@@18.0.1:64)
12-17 09:49:40.837 10092 10184 E AndroidRuntime:        at android.os.Handler.dispatchMessage(Handler.java:107)
12-17 09:49:40.837 10092 10184 E AndroidRuntime:        at android.os.Looper.loopOnce(Looper.java:242)
12-17 09:49:40.837 10092 10184 E AndroidRuntime:        at android.os.Looper.loop(Looper.java:362)
12-17 09:49:40.837 10092 10184 E AndroidRuntime:        at android.os.HandlerThread.run(HandlerThread.java:85)
12-17 09:49:40.837 10092 10184 E AndroidRuntime: Caused by: android.os.RemoteException: Remote stack trace:
12-17 09:49:40.837 10092 10184 E AndroidRuntime:        at com.android.server.am.ActivityManagerService.getIntentSenderWithFeatureAsApp(ActivityManagerService.java:5561)
12-17 09:49:40.837 10092 10184 E AndroidRuntime:        at com.android.server.am.ActivityManagerService.getIntentSenderWithFeature(ActivityManagerService.java:5504)
12-17 09:49:40.837 10092 10184 E AndroidRuntime:        at android.app.IActivityManager$Stub.onTransact$getIntentSenderWithFeature$(IActivityManager.java:11471)
12-17 09:49:40.837 10092 10184 E AndroidRuntime:        at android.app.IActivityManager$Stub.onTransact(IActivityManager.java:3380)
12-17 09:49:40.837 10092 10184 E AndroidRuntime:        at com.android.server.am.ActivityManagerService.onTransact(ActivityManagerService.java:2847)
12-17 09:49:40.837 10092 10184 E AndroidRuntime:

 

Posted

My emby app (3.4.20) also crashes.

I've reinstalled, deleted both cache and data as well.

I do not see this folder /Android/data/com.mb.android/files/logs but I do have a Download folder which contains media that i've downloaded.

I couldn't find any other folders that seemed relevant to Emby.

It happens on both WiFi and Cellular. I typically am listening to music or an audio book, it will stop playing and the app is closed.

The last crash was around 1:19 PM

embyserver(1).7z

Posted
On 12/17/2024 at 7:35 AM, Luke said:

Can you try updating to 3.4.28 and see how things compare? Thanks !

When was it fixed that I couldn't use the Android app

Posted
On 12/22/2024 at 3:51 AM, kooapk said:

When was it fixed that I couldn't use the Android app

@kooapkwhat exactly do you mean by "fixed so you couldn't use" ?

  • 3 weeks later...
Posted
On 12/29/2024 at 5:03 AM, Luke said:

@kooapkwhat exactly do you mean by "fixed so you couldn't use" ?

no

Posted
On 12/28/2024 at 4:03 PM, Luke said:

@kooapkwhat exactly do you mean by "fixed so you couldn't use" ?

@kooapkwhat do you mean by this?

Posted
12 hours ago, Luke said:

@kooapkwhat do you mean by this?

emby crash

Posted

This is the last version, please do not log in to the app during testing

  • 2 weeks later...
Posted

Hi, can you please try 3.4.35 and let us know how things compare? Thanks !

  • 2 weeks later...
Posted
On 1/28/2025 at 4:10 AM, Luke said:

Hi, can you please try 3.4.35 and let us know how things compare? Thanks !

3.4.36 crash

  • Thanks 1
  • 1 month later...
Posted

Hi,

Can you try the latest sideload build and let us know how things compare? 

Thanks !

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...