Android app element crashes on start (4.5 ea)

General
#1

Since recently, (cant recall that I changed anything), element (android chat app) is not starting anymore.
I see the green loading screen and it closes after ~1 second.

I tried reinstalling it, wiping data, installing an old version.

It does not look like an issue of element but of the app suport.

(things that come to my mind: permission issue during app install? Something failed durong sfos upgrade?)

here are some logs: (grepped by vector)

02-05 17:55:25.431   174   205 I ActivityManager: Start
proc 2811:im.vector.app/u0a79 for pre-top-activity {im.v
ector.app/im.vector.application.features.Alias}
02-05 17:55:25.446  2811  2811 E im.vector.app: Not star
ting debugger since process cannot load the jdwp agent.
02-05 17:55:25.517   174   191 I SurfaceFlinger: ALIEN:
new app: im.vector.app vs system
02-05 17:55:25.518  2811  2811 V fb-UnpackingSoSource: l
ocked dso store /data/user/0/im.vector.app/lib-main
02-05 17:55:25.520  2811  2811 I fb-UnpackingSoSource: d
so store is up-to-date: /data/user/0/im.vector.app/lib-m
ain
02-05 17:55:25.520  2811  2811 V fb-UnpackingSoSource: r
eleasing dso store lock for /data/user/0/im.vector.app/l
ib-main
02-05 17:55:25.720  2811  2811 E AndroidRuntime: Process
: im.vector.app, PID: 2811
02-05 17:55:25.720  2811  2811 E AndroidRuntime: java.la
ng.RuntimeException: Unable to create application im.vec
tor.app.VectorApplication: java.lang.RuntimeException: N
o such file or directory in /tmp/realm-java/realm/realm-
library/src/main/cpp/io_realm_internal_OsSharedRealm.cpp
line 107
....
1 Like
Can not run android apps that use realm (e.g. Element) after updating to 4.5
Best matrix client for Sailfish? (Element android app seems bust after last appstore update)
#8

I reinstalled element and looked through the logs. I may have found something interesting:

02-06 10:14:16.333   172   207 E libprocessgroup: set_ti
merslack_ns write failed: Operation not permitted
02-06 10:14:16.393   676   676 E PackageManagerCompat: C
ould not set installer package name for im.vector.app
02-06 10:14:16.393   676   676 E PackageManagerCompat: j
ava.lang.SecurityException: Caller does not have same ce
rt as old installer package com.android.packageinstaller
02-06 10:14:16.393   676   676 E PackageManagerCompat:
at android.os.Parcel.createExceptionOrNull(Parcel.java:2
374)
02-06 10:14:16.393   676   676 E PackageManagerCompat:
at android.os.Parcel.createException(Parcel.java:2358)
02-06 10:14:16.393   676   676 E PackageManagerCompat:
at android.os.Parcel.readException(Parcel.java:2341)
02-06 10:14:16.393   676   676 E PackageManagerCompat:
at android.os.Parcel.readException(Parcel.java:2283)
02-06 10:14:16.393   676   676 E PackageManagerCompat:
at android.content.pm.IPackageManager$Stub$Proxy.setInst
allerPackageName(IPackageManager.java:5874)
02-06 10:14:16.393   676   676 E PackageManagerCompat:
at android.app.ApplicationPackageManager.setInstallerPac
kageName(ApplicationPackageManager.java:2181)
02-06 10:14:16.393   676   676 E PackageManagerCompat:
at org.fdroid.fdroid.compat.PackageManagerCompat.setInst
aller(PackageManagerCompat.java:35)
02-06 10:14:16.393   676   676 E PackageManagerCompat:
at org.fdroid.fdroid.installer.InstallManagerService$3.o
nReceive(InstallManagerService.java:406)
02-06 10:14:16.393   676   676 E PackageManagerCompat:
at androidx.localbroadcastmanager.content.LocalBroadcast
Manager.executePendingBroadcasts(LocalBroadcastManager.j
ava:313)
02-06 10:14:16.393   676   676 E PackageManagerCompat:
at androidx.localbroadcastmanager.content.LocalBroadcast
Manager$1.handleMessage(LocalBroadcastManager.java:121)
02-06 10:14:16.393   676   676 E PackageManagerCompat:
at android.os.Handler.dispatchMessage(Handler.java:106)
02-06 10:14:16.393   676   676 E PackageManagerCompat:
at android.os.Looper.loop(Looper.java:223)
02-06 10:14:16.393   676   676 E PackageManagerCompat:
at android.app.ActivityThread.main(ActivityThread.java:7
656)

Device is a 10II. Maybe I should turn this into a bug report

#9

It looks like the error from last comment is only related to fdroid trying to set the installation method name.

tried other installation methods (aurora store/direct), does not change anything

#10

created a bug report after observing the same issue on a XA2:

2 Likes