litesuits / litesuits/android-lite-orm
Fatal Exception: java.lang.ExceptionInInitializerError
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 1.5k
- Forks
- 359
- PR merge metrics
- No merged PRs in 30d
Description
at com.example.manager.SwitchDBManager.save(Unknown Source)
at com.example.utility.MixpanelUtil.updateUserInfo(Unknown Source)
at com.example.utility.MixpanelUtil.(Unknown Source)
at com.example.utility.MixpanelUtil.updateUserInfo(Unknown Source)
at com.example.Application.onCreate(Unknown Source)
at android.app.Instrumentation.callApplicationOnCreate(Instrumentation.java:1028)
at android.app.ActivityThread.handleBindApplication(ActivityThread.java:5659)
at android.app.ActivityThread.-wrap2(ActivityThread.java)
at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1637)
at android.os.Handler.dispatchMessage(Handler.java:102)
at android.os.Looper.loop(Looper.java:156)
at android.app.ActivityThread.main(ActivityThread.java:6524)
at java.lang.reflect.Method.invoke(Method.java)
at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:941)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:831)
全局使用一个Liteorm,但有多个表,可能存在同时写数据库的情况,就会引起崩溃?
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start at the stack-trace entry points SwitchDBManager.save and MixpanelUtil initialization, then inspect how LiteOrm handles writes to multiple tables during Application.onCreate. Reproduce the reported concurrent database-access path and identify the cause of ExceptionInInitializerError; done means startup no longer crashes under that access pattern.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android, java, sqlite
- Domain
- databases, mobile
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100