-
Notifications
You must be signed in to change notification settings - Fork 216
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
Emit InitialSyncDone
notification to allow client to perform auto-a…
#1832
Emit InitialSyncDone
notification to allow client to perform auto-a…
#1832
Conversation
…ctivation of cross-signing as in Android client Signed-off-by: Nicolas Buquet <[email protected]>
Codecov ReportAttention:
Additional details and impacted files@@ Coverage Diff @@
## develop #1832 +/- ##
===========================================
- Coverage 35.63% 35.61% -0.03%
===========================================
Files 617 617
Lines 96959 96997 +38
Branches 41454 41477 +23
===========================================
- Hits 34552 34543 -9
- Misses 61487 61533 +46
- Partials 920 921 +1 ☔ View full report in Codecov by Sentry. |
Signed-off-by: Nicolas Buquet <[email protected]>
@pixlwave Hello Doug. Can you have a look at this PR. We need it on Tchap. |
Hi Nicolas, I'm a bit confused about the approach of this change. As I understand it, Tchap is a fork of Element iOS, so how come you can't use SessionVerificationListener which does the right thing automatically? |
Thank you for your attention @pixlwave. I was not aware of SessionVerificationListener. I will have a look at it and check if :
Thank you. |
Update to the previous comment. AuthenticationCoordinator is used by OnboardingCoordinator in Element. But OnboardingCoordinator is not used in the custom Onboarding process in Tchap. So, the simple method is to mimic what is done on the Android side, listen to an The best plan would be to use AuthenticationCoordinator in Tchap custom onboarding process, but that's not the short term plan. |
Can't you adopt the SessionVerificationListener in that onboarding process? It handles everything for you, auto-activating, the lot. Alternatively how come you can't listen for the first |
SessionVerificationListener is not very usable (recent Swift not easy to interface with legacy objC). I manage to handle cross-signing auto-activation using kMXSessionDidSyncNotification notification. Thank you for your insight in absence of documentation :-) No more need to emit a new notification Matrix side 👍 |
Emit InitialSyncDone notification to allow client to perform auto-activation of cross-signing as in Android client
Pull Request Checklist