Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Initial sync not working on 1.5.6 and synapse v1.69.0 #7516

Closed
v411e opened this issue Nov 3, 2022 · 27 comments
Closed

Initial sync not working on 1.5.6 and synapse v1.69.0 #7516

v411e opened this issue Nov 3, 2022 · 27 comments
Assignees
Labels
A-Initial sync O-Uncommon Most users are unlikely to come across this or unexpected workflow S-Critical Prevents work, causes data loss and/or has no workaround T-Defect Something isn't working: bugs, crashes, hangs and other reported problems

Comments

@v411e
Copy link

v411e commented Nov 3, 2022

Steps to reproduce

  1. Make a fresh install of 1.5.6 from GitHub releases
  2. Sign in into a homeserver with synapse v1.69.0 running
  3. See the popup "Waiting for server response" for several minutes without any changes

But:
Uninstalled 1.5.6 and reinstalled version 1.5.4 - no problems with new sign in
Element Web - no problems with new sign in
FluffyChat - no problems with new sign in

Outcome

What did you expect?

Working initial sync

What happened instead?

Sync was stuck

Your phone model

Oneplus 8T

Operating system version

Android 12

Application version and app store

1.5.6 apk from GitHub releases

Homeserver

keks.club

Will you send logs?

No

Are you willing to provide a PR?

No

@v411e v411e added the T-Defect Something isn't working: bugs, crashes, hangs and other reported problems label Nov 3, 2022
@akoyaxd
Copy link

akoyaxd commented Nov 3, 2022

Updated to 1.5.6 form 1.5.4 and I get stuck on Launchscreen. Tested Synapse 1.68.0 and 1.70.1.

Pixel 6 on Android 13. (CalyxOS)

Edit: Seems to work now. I shared a picture from my gallery to a group, as I forgot, that my Element was broken.
Not sure if this was somehow "fixing" it or if it was just solved after some time automagicly.

@v411e
Copy link
Author

v411e commented Nov 3, 2022

Yeah, I also first got stuck on the Launchscreen after upgrading

@jmartinesp jmartinesp added A-Initial sync S-Critical Prevents work, causes data loss and/or has no workaround O-Uncommon Most users are unlikely to come across this or unexpected workflow X-Needs-Info labels Nov 4, 2022
@jmartinesp
Copy link
Member

Hi, I'm sorry for the inconvenience. Could you provide some logs so we can pinpoint the issue? We'll try to reproduce it on our side too.

@jmartinesp
Copy link
Member

jmartinesp commented Nov 4, 2022

I tried with synapse 1.71.0rc1 (develop) and I got this (EDIT: it was actually an outdated version without v1.4 spec compliance):

11-04 09:05:11.606  3937  4082 D SYNC/SyncTask: INIT_SYNC Perform server request -- END duration: 58 ms
11-04 09:05:11.606  3937  4082 W SYNC/SyncTask: INIT_SYNC request failure: org.matrix.android.sdk.internal.session.sync.DefaultSyncTask@8b0a053
11-04 09:05:11.607  3937  4082 E SyncAndroidService: ## Sync: sync service did fail true
11-04 09:05:11.607  3937  4082 E SyncAndroidService: ServerError(error=MatrixError(code=M_UNKNOWN, message=Additional properties are not allowed ('unread_thread_notifications' was unexpected)
11-04 09:05:11.607  3937  4082 E SyncAndroidService:
11-04 09:05:11.607  3937  4082 E SyncAndroidService: Failed validating 'additionalProperties' in schema['properties']['room']['properties']['timeline']:
11-04 09:05:11.607  3937  4082 E SyncAndroidService:     {'additionalProperties': False,
11-04 09:05:11.607  3937  4082 E SyncAndroidService:      'properties': {'contains_url': {'type': 'boolean'},
11-04 09:05:11.607  3937  4082 E SyncAndroidService:                     'include_redundant_members': {'type': 'boolean'},
11-04 09:05:11.607  3937  4082 E SyncAndroidService:                     'lazy_load_members': {'type': 'boolean'},
11-04 09:05:11.607  3937  4082 E SyncAndroidService:                     'limit': {'type': 'number'},
11-04 09:05:11.607  3937  4082 E SyncAndroidService:                     'not_rooms': {'$ref': '#/definitions/room_id_array'},
11-04 09:05:11.607  3937  4082 E SyncAndroidService:                     'not_senders': {'$ref': '#/definitions/user_id_array'},
11-04 09:05:11.607  3937  4082 E SyncAndroidService:                     'not_types': {'items': {'type': 'string'},
11-04 09:05:11.607  3937  4082 E SyncAndroidService:                                   'type': 'array'},
11-04 09:05:11.607  3937  4082 E SyncAndroidService:                     'org.matrix.labels': {'items': {'type': 'string'},
11-04 09:05:11.607  3937  4082 E SyncAndroidService:                                           'type': 'array'},
11-04 09:05:11.607  3937  4082 E SyncAndroidService:                     'org.matrix.not_labels': {'items': {'type': 'string'},
11-04 09:05:11.607  3937  4082 E SyncAndroidService:                                               'type': 'array'},
11-04 09:05:11.607  3937  4082 E SyncAndroidService:                     'related_by_rel_types': {'items': {'type': 'string'},
11-04 09:05:11.607  3937  4082 E SyncAndroidService:                                              'type': 'array'},
11-04 09:05:11.607  3937  4082 E SyncAndroidService:                     'related_by_senders': {'items': {'type': 'string'},
11-04 09:05:11.607  3937  4082 E SyncAndroidService:                                            'type': 'array'},
11-04 09:05:11.607  3937  4082 E SyncAndroidService:                     'rooms': {'$ref': '#/definitions/room_id_array'},
11-04 09:05:11.607  3937  4082 E SyncAndroidService:                     'senders': {'$ref': '#/definitions/user_id_array'},
11-04 09:05:11.607  3937  4082 E SyncAndroidService:                     'types': {'items': {'type': 'string'},
11-04 09:05:11.607  3937  4082 E SyncAndroidService:                               'type': 'array'}},
11-04 09:05:11.607  3937  4082 E SyncAndroidService:      'type': 'object'}
11-04 09:05:11.607  3937  4082 E SyncAndroidService:
11-04 09:05:11.607  3937  4082 E SyncAndroidService: On instance['room']['timeline']:
11-04 09:05:11.607  3937  4082 E SyncAndroidService:     {'unread_thread_notifications': True}, consentUri=null, limitType=null, adminUri=null, retryAfterMillis=null, isSoftLogout=null, newLookupPepper=null, session=null, completedStages=null, flows=null, params=null), httpCode=400)
11-04 09:05:11.607  3937  4082 E SyncAndroidService: 	at org.matrix.android.sdk.internal.network.RetrofitExtensionsKt.toFailure(RetrofitExtensions.kt:103)
11-04 09:05:11.607  3937  4082 E SyncAndroidService: 	at org.matrix.android.sdk.internal.network.RetrofitExtensionsKt.toFailure(RetrofitExtensions.kt:59)
11-04 09:05:11.607  3937  4082 E SyncAndroidService: 	at org.matrix.android.sdk.internal.session.sync.DefaultSyncTask.downloadInitSyncResponse(SyncTask.kt:224)
11-04 09:05:11.607  3937  4082 E SyncAndroidService: 	at org.matrix.android.sdk.internal.session.sync.DefaultSyncTask.access$downloadInitSyncResponse(SyncTask.kt:64)
11-04 09:05:11.607  3937  4082 E SyncAndroidService: 	at org.matrix.android.sdk.internal.session.sync.DefaultSyncTask$downloadInitSyncResponse$1.invokeSuspend(Unknown Source:15)
11-04 09:05:11.607  3937  4082 E SyncAndroidService: 	at kotlin.coroutines.jvm.internal.BaseContinuationImpl.resumeWith(ContinuationImpl.kt:33)
11-04 09:05:11.607  3937  4082 E SyncAndroidService: 	at kotlinx.coroutines.DispatchedTask.run(DispatchedTask.kt:106)
11-04 09:05:11.607  3937  4082 E SyncAndroidService: 	at kotlinx.coroutines.internal.LimitedDispatcher.run(LimitedDispatcher.kt:42)
11-04 09:05:11.607  3937  4082 E SyncAndroidService: 	at kotlinx.coroutines.scheduling.TaskImpl.run(Tasks.kt:95)
11-04 09:05:11.607  3937  4082 E SyncAndroidService: 	at kotlinx.coroutines.scheduling.CoroutineScheduler.runSafely(CoroutineScheduler.kt:570)
11-04 09:05:11.607  3937  4082 E SyncAndroidService: 	at kotlinx.coroutines.scheduling.CoroutineScheduler$Worker.executeTask(CoroutineScheduler.kt:750)
11-04 09:05:11.607  3937  4082 E SyncAndroidService: 	at kotlinx.coroutines.scheduling.CoroutineScheduler$Worker.runWorker(CoroutineScheduler.kt:677)
11-04 09:05:11.607  3937  4082 E SyncAndroidService: 	at kotlinx.coroutines.scheduling.CoroutineScheduler$Worker.run(CoroutineScheduler.kt:664)
11-04 09:05:11.607  3937  4082 E SyncAndroidService: Caused by: java.lang.RuntimeException: MatrixError(code=M_UNKNOWN, message=Additional properties are not allowed ('unread_thread_notifications' was unexpected)
11-04 09:05:11.607  3937  4082 E SyncAndroidService:
11-04 09:05:11.607  3937  4082 E SyncAndroidService: Failed validating 'additionalProperties' in schema['properties']['room']['properties']['timeline']:
11-04 09:05:11.607  3937  4082 E SyncAndroidService:     {'additionalProperties': False,
11-04 09:05:11.607  3937  4082 E SyncAndroidService:      'properties': {'contains_url': {'type': 'boolean'},
11-04 09:05:11.607  3937  4082 E SyncAndroidService:                     'include_redundant_members': {'type': 'boolean'},
11-04 09:05:11.607  3937  4082 E SyncAndroidService:                     'lazy_load_members': {'type': 'boolean'},
11-04 09:05:11.607  3937  4082 E SyncAndroidService:                     'limit': {'type': 'number'},
11-04 09:05:11.607  3937  4082 E SyncAndroidService:                     'not_rooms': {'$ref': '#/definitions/room_id_array'},
11-04 09:05:11.607  3937  4082 E SyncAndroidService:                     'not_senders': {'$ref': '#/definitions/user_id_array'},
11-04 09:05:11.607  3937  4082 E SyncAndroidService:                     'not_types': {'items': {'type': 'string'},
11-04 09:05:11.607  3937  4082 E SyncAndroidService:                                   'type': 'array'},
11-04 09:05:11.607  3937  4082 E SyncAndroidService:                     'org.matrix.labels': {'items': {'type': 'string'},
11-04 09:05:11.607  3937  4082 E SyncAndroidService:                                           'type': 'array'},
11-04 09:05:11.607  3937  4082 E SyncAndroidService:                     'org.matrix.not_labels': {'items': {'type': 'string'},
11-04 09:05:11.607  3937  4082 E SyncAndroidService:                                               'type': 'array'},
11-04 09:05:11.607  3937  4082 E SyncAndroidService:                     'related_by_rel_types': {'items': {'type': 'string'},
11-04 09:05:11.607  3937  4082 E SyncAndroidService:                                              'type': 'array'},
11-04 09:05:11.607  3937  4082 E SyncAndroidService:                     'related_by_senders': {'items': {'type': 'string'},
11-04 09:05:11.607  3937  4082 E SyncAndroidService:                                            'type': 'array'},
11-04 09:05:11.607  3937  4082 E SyncAndroidService:                     'rooms': {'$ref': '#/definitions/room_id_array'},
11-04 09:05:11.607  3937  4082 E SyncAndroidService:                     'senders': {'$ref': '#/definitions/user_id_array'},
11-04 09:05:11.607  3937  4082 E SyncAndroidService:                     'types': {'items': {'type': 'string'},
11-04 09:05:11.607  3937  4082 E SyncAndroidService:                               'type': 'array'}},
11-04 09:05:11.607  3937  4082 E SyncAndroidService:      'type': 'object'}
11-04 09:05:11.607  3937  4082 E SyncAndroidService:
11-04 09:05:11.607  3937  4082 E SyncAndroidService: On instance['room']['timeline']:
11-04 09:05:11.607  3937  4082 E SyncAndroidService:     {'unread_thread_notifications': True}, consentUri=null, limitType=null, adminUri=null, retryAfterMillis=null, isSoftLogout=null, newLookupPepper=null, session=null, completedStages=null, flows=null, params=null)
11-04 09:05:11.607  3937  4082 E SyncAndroidService: 	... 13 more
11-04 09:05:11.611  3937  3937 I SyncAndroidService: ## Sync: onDestroy() [im.vector.app.core.services.VectorSyncAndroidService@704fe8c] periodic:false preventReschedule:false

@GreenReaper
Copy link

GreenReaper commented Nov 4, 2022

Not sure if it is the same issue, but I updated the store beta client on Android 10 (Redmi Note Pro 6; LineageOS) and I now only get new messages via notifications; the messages are not appearing when I open the app, only those from before the update.

I can send to a channel and it appears on my client, but I get no read receipta. When I open a channel, the update cycling bar persists for ~10 seconds. I have sent a bug report from the client with logs.

@jmartinesp
Copy link
Member

@GreenReaper according to the contents of the rageshake, it looks like it's the same issue.

@GreenReaper
Copy link

Thanks for letting me know. FWIW I toggled MSC3061 off in labs, and that seems to have forced a sync that received the missing messages, but this is a low traffic server so I don't know if that resolved the general issue of not receiving new messages.

@squahtx
Copy link

squahtx commented Nov 4, 2022

The error

11-04 09:05:11.607  3937  4082 E SyncAndroidService: Failed validating 'additionalProperties' in schema['properties']['room']['properties']['timeline']:
11-04 09:05:11.607  3937  4082 E SyncAndroidService:     {'additionalProperties': False,
11-04 09:05:11.607  3937  4082 E SyncAndroidService:      'properties': {'contains_url': {'type': 'boolean'},
11-04 09:05:11.607  3937  4082 E SyncAndroidService:                     'include_redundant_members': {'type': 'boolean'},
11-04 09:05:11.607  3937  4082 E SyncAndroidService:                     'lazy_load_members': {'type': 'boolean'},
11-04 09:05:11.607  3937  4082 E SyncAndroidService:                     'limit': {'type': 'number'},
11-04 09:05:11.607  3937  4082 E SyncAndroidService:                     'not_rooms': {'$ref': '#/definitions/room_id_array'},
11-04 09:05:11.607  3937  4082 E SyncAndroidService:                     'not_senders': {'$ref': '#/definitions/user_id_array'},
11-04 09:05:11.607  3937  4082 E SyncAndroidService:                     'not_types': {'items': {'type': 'string'},
11-04 09:05:11.607  3937  4082 E SyncAndroidService:                                   'type': 'array'},
11-04 09:05:11.607  3937  4082 E SyncAndroidService:                     'org.matrix.labels': {'items': {'type': 'string'},
11-04 09:05:11.607  3937  4082 E SyncAndroidService:                                           'type': 'array'},
11-04 09:05:11.607  3937  4082 E SyncAndroidService:                     'org.matrix.not_labels': {'items': {'type': 'string'},
11-04 09:05:11.607  3937  4082 E SyncAndroidService:                                               'type': 'array'},
11-04 09:05:11.607  3937  4082 E SyncAndroidService:                     'related_by_rel_types': {'items': {'type': 'string'},
11-04 09:05:11.607  3937  4082 E SyncAndroidService:                                              'type': 'array'},
11-04 09:05:11.607  3937  4082 E SyncAndroidService:                     'related_by_senders': {'items': {'type': 'string'},
11-04 09:05:11.607  3937  4082 E SyncAndroidService:                                            'type': 'array'},
11-04 09:05:11.607  3937  4082 E SyncAndroidService:                     'rooms': {'$ref': '#/definitions/room_id_array'},
11-04 09:05:11.607  3937  4082 E SyncAndroidService:                     'senders': {'$ref': '#/definitions/user_id_array'},
11-04 09:05:11.607  3937  4082 E SyncAndroidService:                     'types': {'items': {'type': 'string'},
11-04 09:05:11.607  3937  4082 E SyncAndroidService:                               'type': 'array'}},
11-04 09:05:11.607  3937  4082 E SyncAndroidService:      'type': 'object'}

is coming from Synapse because unread_thread_notifications was specified in the sync filter, but older versions of Synapse do not understand it.

@squahtx
Copy link

squahtx commented Nov 4, 2022

Filed as matrix-org/synapse#14365

@squahtx
Copy link

squahtx commented Nov 4, 2022

On the Synapse side, we ought to be more accepting of unrecognized fields in /sync filters (matrix-org/synapse#14365).

On the Element Android side, we can determine whether it's okay to use the unread_thread_notifications filter option by checking for "v1.4" in /_matrix/client/versions's list of supported spec versions.*

* The spec at https://spec.matrix.org/latest/client-server-api/#post_matrixclientv3useruseridfilter says that the field was added in 1.4.

@SapuSeven
Copy link

SapuSeven commented Nov 4, 2022

Is there a known workaround in the meantime? I use the App daily and this issue makes it unusable.

@jmartinesp
Copy link
Member

Is there a workaround for this issue? I use the App daily and this makes it unusable.

@GreenReaper mentioned above:

FWIW I toggled MSC3061 off in labs, and that seems to have forced a sync that received the missing messages
But I haven't been able to verify if this fixes or work arounds the issue.

I think for now the best option is to go back to the previous version (1.5.4 or before). We're working on a fix, but it might take a while to be published.

@v411e
Copy link
Author

v411e commented Nov 4, 2022

The bug just made it into the (Beta?) Playstore and auto-update broke my Element again ^^

@starcraft66
Copy link

Had to leave the element beta program on google play to downgrade to 1.5.4 and log in on my new phone.

@kylrth
Copy link

kylrth commented Nov 6, 2022

It's a big problem that this bug was caught but not stopped from arriving to the main Play Store channel. The app is completely unusable for a large number of people now. Isn't the point of the beta channel to catch these sorts of bugs before releasing to everyone? This is not true, the bug never reached the main channel.

@kylrth
Copy link

kylrth commented Nov 6, 2022

Is this resolved with a newer version of synapse?

@starcraft66
Copy link

@kylrth I upgraded my home server in attempt to unblock some of my users and that fixed it for them.

@bmarty
Copy link
Member

bmarty commented Nov 7, 2022

It's a big problem that this bug was caught but not stopped from arriving to the main Play Store channel. The app is completely unusable for a large number of people now. Isn't the point of the beta channel to catch these sorts of bugs before releasing to everyone?

On the PlayStore, the bug is not in the production channel, but only visible by users who join the beta program (i.e. about 10k users).

We are working on a fix before releasing to production.

@fedrunov fedrunov self-assigned this Nov 7, 2022
@kylrth
Copy link

kylrth commented Nov 7, 2022

@bmarty sorry, you're right. It turns out my users who were also seeing the problem were also on the beta channel. My bad.

@karolyi
Copy link

karolyi commented Nov 8, 2022

Can confirm with element-android 1.5.6 from FDroid and synapse v1.69.0. Had to downgrade to 1.5.4 to get it working again.

@jmartinesp
Copy link
Member

This should be fixed on the app side on v1.5.7 which is already available on Play Store and GH releases page, it will soon come to F-droid too. Please re-open if the issue appears again.

@akoyaxd
Copy link

akoyaxd commented Nov 9, 2022

After updating from v1.5.6 to v1.5.7 from the play store I am again stuck in the launch screen. I can't use rage shake there..

Synapse v1.70.1
Android 13 (CalyxOS)
Pixel 6

logcat | grep vector

11-09 12:25:32.935 12578 12578 I AppLocaleUtil: Can display preference - [im.vector.app] : isDisallowedPackage : false / isSignedWithPlatformKey : false / hasLauncherEntry : true / canDisplay : false
11-09 12:25:32.935 12578 12578 I AppLocaleUtil: Can display preference - [im.vector.app] : isDisallowedPackage : false / isSignedWithPlatformKey : false / hasLauncherEntry : true / canDisplay : false
11-09 12:25:33.019 12578 12578 I AppLocaleUtil: Can display preference - [im.vector.app] : isDisallowedPackage : false / isSignedWithPlatformKey : false / hasLauncherEntry : true / canDisplay : false
11-09 12:25:33.289  1838  4274 W PackageConfigPersister: App-specific configuration not found for packageName: im.vector.app and userId: 0
11-09 12:25:33.665  7401  7569 I Role    : im.vector.app not qualified for android.app.role.HOME due to missing RequiredComponent{mIntentFilterData=IntentFilterData{mAction='android.intent.action.MAIN', mCategories='[android.intent.category.HOME]', mDataScheme='null', mDataType='null'}, mMinTargetSdkVersion=1, mPermission='null', mQueryFlags=0, mMetaData=[]}
11-09 12:25:33.666  7401  7569 I Role    : im.vector.app not qualified for android.app.role.DIALER due to missing RequiredComponent{mIntentFilterData=IntentFilterData{mAction='android.intent.action.DIAL', mCategories='[]', mDataScheme='null', mDataType='null'}, mMinTargetSdkVersion=1, mPermission='null', mQueryFlags=0, mMetaData=[]}
11-09 12:25:33.667  7401  7569 I Role    : im.vector.app not qualified for android.app.role.SMS due to missing RequiredComponent{mIntentFilterData=IntentFilterData{mAction='android.provider.Telephony.SMS_DELIVER', mCategories='[]', mDataScheme='null', mDataType='null'}, mMinTargetSdkVersion=1, mPermission='android.permission.BROADCAST_SMS', mQueryFlags=0, mMetaData=[]}
11-09 12:25:34.421  1838  4368 W PackageConfigPersister: App-specific configuration not found for packageName: im.vector.app and userId: 0
11-09 12:25:34.990  1838  4372 W PackageConfigPersister: App-specific configuration not found for packageName: im.vector.app and userId: 0
11-09 12:25:35.933 12578 12578 D AppButtonsPrefCtl: Stopping package im.vector.app
11-09 12:25:35.934  1838  4372 I ActivityManager: Force stopping im.vector.app appid=10215 user=0: from pid 12578
11-09 12:25:35.939 12578 12578 D AppButtonsPrefCtl: Sending broadcast to query restart status for im.vector.app
11-09 12:25:35.944  2485  2485 D CarrierSvcBindHelper: onHandleForceStop: [im.vector.app]
11-09 12:25:36.094  1838  2714 W PackageConfigPersister: App-specific configuration not found for packageName: im.vector.app and userId: 0
11-09 12:25:36.096 12578 12578 D AppButtonsPrefCtl: Sending broadcast to query restart status for im.vector.app
11-09 12:25:36.098 12578 12578 D AppButtonsPrefCtl: Sending broadcast to query restart status for im.vector.app
11-09 12:25:36.228  1838  4356 W PackageConfigPersister: App-specific configuration not found for packageName: im.vector.app and userId: 0
11-09 12:25:36.232 12578 12578 D AppButtonsPrefCtl: Sending broadcast to query restart status for im.vector.app
11-09 12:25:36.234 12578 12578 D AppButtonsPrefCtl: Got broadcast response: Restart status for im.vector.app false
11-09 12:25:36.245 12578 12578 D AppButtonsPrefCtl: Got broadcast response: Restart status for im.vector.app false
11-09 12:25:36.245 12578 12578 D AppButtonsPrefCtl: Got broadcast response: Restart status for im.vector.app false
11-09 12:25:36.258 12578 12578 D AppButtonsPrefCtl: Got broadcast response: Restart status for im.vector.app false
11-09 12:25:36.640  1838  4356 I ActivityTaskManager: START u0 {act=android.intent.action.MAIN cat=[android.intent.category.LAUNCHER] flg=0x10000000 pkg=im.vector.app cmp=im.vector.app/im.vector.application.features.Alias} from uid 1000
11-09 12:25:36.654  1838  4356 D CoreBackPreview: Window{db77a0a u0 Splash Screen im.vector.app}: Setting back callback OnBackInvokedCallbackInfo{mCallback=android.window.IOnBackInvokedCallback$Stub$Proxy@1db2898, mPriority=0}
11-09 12:25:36.664  1838  1871 I ActivityManager: Start proc 12684:im.vector.app/u0a215 for next-top-activity {im.vector.app/im.vector.application.features.Alias}
11-09 12:25:36.671 12684 12684 E im.vector.app: Not starting debugger since process cannot load the jdwp agent.
11-09 12:25:36.692 12684 12684 V GraphicsEnvironment: ANGLE Developer option for 'im.vector.app' set to: 'default'
11-09 12:25:36.692 12684 12684 V GraphicsEnvironment: ANGLE GameManagerService for im.vector.app: false
11-09 12:25:36.702 12684 12684 V fb-UnpackingSoSource: locked dso store /data/user/0/im.vector.app/lib-main
11-09 12:25:36.702 12684 12684 I fb-UnpackingSoSource: dso store is up-to-date: /data/user/0/im.vector.app/lib-main
11-09 12:25:36.702 12684 12684 V fb-UnpackingSoSource: releasing dso store lock for /data/user/0/im.vector.app/lib-main
11-09 12:25:36.807 12684 12684 W pool-24-thread-: type=1400 audit(0.0:15033): avc: denied { read } for name="version" dev="proc" ino=4026532008 scontext=u:r:untrusted_app:s0:c215,c256,c512,c768 tcontext=u:object_r:proc_version:s0 tclass=file permissive=0 app=im.vector.app
11-09 12:25:36.836 12684 12817 D vulkan  : searching for layers in '/data/app/~~0t9teItFFqVleupuX_lTaQ==/im.vector.app-3tJkuG4xfH1bgdpl2ytndQ==/lib/arm64'
11-09 12:25:36.836 12684 12817 D vulkan  : searching for layers in '/data/app/~~0t9teItFFqVleupuX_lTaQ==/im.vector.app-3tJkuG4xfH1bgdpl2ytndQ==/base.apk!/lib/arm64-v8a'
11-09 12:25:37.015  1838  4363 D ConnectivityService: requestNetwork for uid/pid:10215/12684 activeRequest: null callbackRequest: 11768 [NetworkRequest [ REQUEST id=11769, [ Capabilities: INTERNET&NOT_RESTRICTED&TRUSTED&NOT_VCN_MANAGED Uid: 10215 RequestorUid: 10215 RequestorPkg: im.vector.app UnderlyingNetworks: Null] ]] callback flags: 0 order: 2147483647
11-09 12:25:37.018  1838  2114 D WifiNetworkFactory: got request NetworkRequest [ REQUEST id=11769, [ Capabilities: INTERNET&NOT_RESTRICTED&TRUSTED&NOT_VCN_MANAGED Uid: 10215 RequestorUid: 10215 RequestorPkg: im.vector.app UnderlyingNetworks: Null] ]
11-09 12:25:37.018  1838  2114 D UntrustedWifiNetworkFactory: got request NetworkRequest [ REQUEST id=11769, [ Capabilities: INTERNET&NOT_RESTRICTED&TRUSTED&NOT_VCN_MANAGED Uid: 10215 RequestorUid: 10215 RequestorPkg: im.vector.app UnderlyingNetworks: Null] ]
11-09 12:25:37.019  1838  2114 D OemPaidWifiNetworkFactory: got request NetworkRequest [ REQUEST id=11769, [ Capabilities: INTERNET&NOT_RESTRICTED&TRUSTED&NOT_VCN_MANAGED Uid: 10215 RequestorUid: 10215 RequestorPkg: im.vector.app UnderlyingNetworks: Null] ]
11-09 12:25:37.019  1838  2114 D MultiInternetWifiNetworkFactory: got request NetworkRequest [ REQUEST id=11769, [ Capabilities: INTERNET&NOT_RESTRICTED&TRUSTED&NOT_VCN_MANAGED Uid: 10215 RequestorUid: 10215 RequestorPkg: im.vector.app UnderlyingNetworks: Null] ]
11-09 12:25:47.408 12684 12697 W im.vector.app: Cleared Reference was only reachable from finalizer (only reported once)
11-09 12:25:47.415 12684 12697 I im.vector.app: Background concurrent copying GC freed 336699(15MB) AllocSpace objects, 76(2532KB) LOS objects, 78% free, 6578KB/30MB, paused 101us,46us total 137.714ms
11-09 12:25:54.898  1838  1838 W JobServiceContext: Time-out while trying to bind 6924ed #u0a215/102205 im.vector.app/androidx.work.impl.background.systemjob.SystemJobService, dropping.
11-09 12:25:54.907  1838  1838 W JobServiceContext: Time-out while trying to bind a4022e9 #u0a215/102206 im.vector.app/androidx.work.impl.background.systemjob.SystemJobService, dropping.
11-09 12:26:14.927  1838  1870 W ActivityManager: Timeout executing service: ServiceRecord{324f70 u0 im.vector.app/androidx.work.impl.background.systemjob.SystemJobService}
11-09 12:26:15.537 12684 12691 I im.vector.app: Thread[5,tid=12691,WaitingInMainSignalCatcherLoop,Thread*=0xb400007139b8ff50,peer=0x14e00740,"Signal Catcher"]: reacting to signal 3
11-09 12:26:15.537 12684 12691 I im.vector.app: 
11-09 12:26:15.778 12684 12691 I im.vector.app: Wrote stack traces to tombstoned
11-09 12:26:16.827  1838 13259 W ActivityManager: Missing app error report, app = im.vector.app crashing = false notResponding = true
11-09 12:26:21.828  1838 13259 W ActivityManager: Missing app error report, app = im.vector.app crashing = false notResponding = true
11-09 12:26:24.723 13049 13077 I BackupNotificationManager: Opt-out APK for im.vector.app
11-09 12:26:26.830  1838 13259 W ActivityManager: Missing app error report, app = im.vector.app crashing = false notResponding = true
11-09 12:26:31.831  1838  2721 W ActivityManager: Missing app error report, app = im.vector.app crashing = false notResponding = true
11-09 12:26:31.845 10454 13370 D InstalledAppProviderSer: deleteAppFromDb im.vector.app
11-09 12:26:32.067 10454 13370 D InstalledAppProviderSer: insertAppIntoDb im.vector.app
11-09 12:26:35.094  1838 12961 E ActivityManager: ANR in im.vector.app
11-09 12:26:35.094  1838 12961 E ActivityManager: Reason: executing service im.vector.app/androidx.work.impl.background.systemjob.SystemJobService
11-09 12:26:35.094  1838 12961 E ActivityManager:   11% 12684/im.vector.app: 9.4% user + 2.3% kernel / faults: 15290 minor 122 major
11-09 12:26:35.096  1838 12961 D ActivityManager: Completed ANR of im.vector.app in 20167ms, latency 1ms
11-09 12:26:35.121  1838  1860 D CoreBackPreview: Window{4483232 u0 Application Not Responding: im.vector.app}: Setting back callback OnBackInvokedCallbackInfo{mCallback=android.window.WindowOnBackInvokedDispatcher$OnBackInvokedCallbackWrapper@6b693f5, mPriority=0}
11-09 12:26:37.439 13049 13077 D ApkBackup: Backed up new APK of im.vector.app with version 40105072.
11-09 12:26:37.912  1838 13145 W PackageConfigPersister: App-specific configuration not found for packageName: im.vector.app and userId: 0

@SapuSeven
Copy link

For me, the updated version works again for messaging, but i haven't tested the login

@felschr
Copy link

felschr commented Nov 9, 2022

I, too, get stuck on the launch screen after updating from 1.5.3 to 1.5.7 from Google Play like @akoyaxd.
I'm running CalyxOS 4.2.7 (Android 13) on a Pixel 3.

@jmartinesp
Copy link
Member

That seems like a different issue, could you open a new issue with that info/logs? Thank you, and sorry for the inconvenience.

@akoyaxd
Copy link

akoyaxd commented Nov 9, 2022

Yes, I will open one

@akoyaxd
Copy link

akoyaxd commented Nov 9, 2022

New issue: #7557

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-Initial sync O-Uncommon Most users are unlikely to come across this or unexpected workflow S-Critical Prevents work, causes data loss and/or has no workaround T-Defect Something isn't working: bugs, crashes, hangs and other reported problems
Projects
None yet