Countly / Countly/countly-sdk-android

Crash in migration helper

Open
#511 5 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Java
Stars
696
Forks
290
Avg merge
9h 15m
Merged PRs (30d)
8

Description

Hello! On a fresh install, the countly sdk throws an exception, like so:

Process: com.app, PID: 26888
java.lang.AssertionError
	at ly.count.android.sdk.MigrationHelper.doWork(MigrationHelper.java:55)
	at ly.count.android.sdk.Countly.init(Countly.java:550)
	at com.app.MainApplication.initCountly(MainApplication.kt:699)
	at com.app.MainApplication.access$initCountly(MainApplication.kt:163)
	at com.app.MainApplication$onCreate$1$initJobs$2.invokeSuspend(MainApplication.kt:598)
	at kotlin.coroutines.jvm.internal.BaseContinuationImpl.resumeWith(ContinuationImpl.kt:34)
	at kotlinx.coroutines.DispatchedTask.run(DispatchedTask.kt:100)
	at kotlinx.coroutines.internal.LimitedDispatcher$Worker.run(LimitedDispatcher.kt:124)
	at kotlinx.coroutines.scheduling.TaskImpl.run(Tasks.kt:89)
	at kotlinx.coroutines.scheduling.CoroutineScheduler.runSafely(CoroutineScheduler.kt:586)
	at kotlinx.coroutines.scheduling.CoroutineScheduler$Worker.executeTask(CoroutineScheduler.kt:820)
	at kotlinx.coroutines.scheduling.CoroutineScheduler$Worker.runWorker(CoroutineScheduler.kt:717)
	at kotlinx.coroutines.scheduling.CoroutineScheduler$Worker.run(CoroutineScheduler.kt:704)

Occurs across several different test devices.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing the fresh-install crash and inspect MigrationHelper.java at line 55, then trace how Countly.init in Countly.java reaches it. Determine why the assertion is triggered on fresh installs and verify that initialization completes without crashing on the affected test devices.

Written by the indexing model from the issue text.

Assessment

Tech stack
java
Domain
mobile
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.