Intermittent "Nostr is not initialized" Exception During App Startup

[Catrya]

The app occasionally crashes during startup with the error Exception: Nostr is not initialized. Call init() first. This appears to be a race condition that occurs intermittently when the app is launched.

  Exception: Nostr is not initialized. Call init() first.
  #0   NostrService.subscribeToEvents (package:mostro_mobile/services/nostr_service.dart:170:7)
  #1   SubscriptionManager.subscribe
  (package:mostro_mobile/features/subscriptions/subscription_manager.dart:181:33)
  #2   SubscriptionManager._updateSubscription
  (package:mostro_mobile/features/subscriptions/subscription_manager.dart:106:7)
  #3   SubscriptionManager._updateAllSubscriptions
  (package:mostro_mobile/features/subscriptions/subscription_manager.dart:82:7)
  #4   SubscriptionManager._initSessionListener.
  (package:mostro_mobile/features/subscriptions/subscription_manager.dart:43:9)

This is intermittent and have low frequency, occurs occasionally, not on every app launch. if user restarts the app is working fine again, but if occurs when configuring a new Mostro instance, the error may persist across multiple app restarts.

[kufre19]

hey @Catrya, good day to you. I came across this issue alot was wondering if i could be assigned to it

[Catrya]

hey @Catrya, good day to you. I came across this issue alot was wondering if i could be assigned to it

Hi @kufre19 it's great that you want to take ths issue. Before you're assigned it, I should mention that this is a complex bug that requires a detailed analysis of the process flow when the app starts, and probably changing the order in which they occur to resolve the race condition, which could be critical.

My recommendation would be that before taking on issues as complicated as this one, you choose some of the ones with the Good First Issue tag, so you can familiarize yourself more with working with this mobile client.

But if you insist on taking this issue, I can assign it to you without any problem.

[kufre19]

hmm well spending a few more days getting to know the architecture of the mobile client more will certainly be helpful in the process of identifying the exact reason the race condition occurs, please assign me this other issue issue 358 but still i'd like to circle back to this asap, it could be problematic for non technical users