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

Prepare release 11.1 #1342

Merged
merged 10 commits into from
Jan 31, 2025
Merged

Prepare release 11.1 #1342

merged 10 commits into from
Jan 31, 2025

Conversation

HashEngineering
Copy link
Collaborator

Issue being fixed or feature implemented

Related PR's and Dependencies

Screenshots / Videos

How Has This Been Tested?

  • QA (Mobile Team)

Checklist:

  • I have performed a self-review of my own code and added comments where necessary
  • I have added or updated relevant unit/integration/functional/e2e tests

Comment on lines 1277 to 1289
// unregister receivers on the main thread
unregisterReceiver(tickReceiver)
unregisterReceiver(connectivityReceiver)
cleanupDeferred = CompletableDeferred()
serviceScope.launch {
try {
onCreateCompleted.await() // wait until onCreate is finished
WalletApplication.scheduleStartBlockchainService(this@BlockchainServiceImpl) //disconnect feature
unregisterReceiver(tickReceiver)
application.wallet!!.removeChangeEventListener(walletEventListener)
application.wallet!!.removeCoinsSentEventListener(walletEventListener)
application.wallet!!.removeCoinsReceivedEventListener(walletEventListener)
config.unregisterOnSharedPreferenceChangeListener(sharedPrefsChangeListener)
unregisterReceiver(connectivityReceiver)
platformSyncService.shutdown()
Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This change is to solve problems with unregistering receivers. There were exceptions about leaking receivers and unregistering receivers that were not registered.

This was probably a result of running the cleanup in a coroutine instead of before onDestroy finishes execution.

Service de.schildbach.wallet.service.BlockchainServiceImpl has leaked IntentReceiver de.schildbach.wallet.service.BlockchainServiceImpl$tickReceiver$1@3257bc5 that was originally registered here. Are you missing a call to unregisterReceiver()?
android.app.IntentReceiverLeaked: Service de.schildbach.wallet.service.BlockchainServiceImpl has leaked IntentReceiver de.schildbach.wallet.service.BlockchainServiceImpl$tickReceiver$1@3257bc5 that was originally registered here. Are you missing a call to unregisterReceiver()?

at android.app.LoadedApk$ReceiverDispatcher.<init>(LoadedApk.java:1839)
at android.app.LoadedApk.getReceiverDispatcher(LoadedApk.java:1601)
at android.app.ContextImpl.registerReceiverInternal(ContextImpl.java:1840)
at android.app.ContextImpl.registerReceiver(ContextImpl.java:1792)
at android.app.ContextImpl.registerReceiver(ContextImpl.java:1780)
at android.content.ContextWrapper.registerReceiver(ContextWrapper.java:755)
at de.schildbach.wallet.service.BlockchainServiceImpl$onCreate$1.invokeSuspend(BlockchainServiceImpl.kt:1097)

Comment on lines -414 to +417
.flatMapLatest { _ ->
init()

if (!hasIdentity) {
return@flatMapLatest flowOf(emptyList())
}

val userId = blockchainIdentity.uniqueIdString
.filter { it.creationState >= BlockchainIdentityData.CreationState.DONE }
.flatMapLatest { identityData ->
val userId = identityData.userId!!
Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Found a crash due during wallet restoration. Let's make sure that restoration of the identity is finished first.

@HashEngineering HashEngineering self-assigned this Jan 31, 2025
Copy link
Member

@Syn-McJ Syn-McJ left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good

@HashEngineering HashEngineering merged commit b91c776 into master Jan 31, 2025
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants