microg / microg/AppleWifiNlpBackend
BackendService NullPointerException
Open
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 90
- Forks
- 15
- PR merge metrics
- No merged PRs in 30d
Description
01-28 16:46:18.250 12257 28801 W AppleNlpBackendService: java.lang.NullPointerException
01-28 16:46:18.250 12257 28801 W AppleNlpBackendService: at org.microg.nlp.backend.apple.BackendService$1.run(BackendService.java:57)
01-28 16:46:18.250 12257 28801 W AppleNlpBackendService: at java.lang.Thread.run(Thread.java:841)
01-28 16:46:18.250 12257 28801 W dalvikvm: threadid=13: thread exiting with uncaught exception (group=0x4160ed58)
01-28 16:46:18.251 12257 28801 E AndroidRuntime: FATAL EXCEPTION: Thread-1751
01-28 16:46:18.251 12257 28801 E AndroidRuntime: Process: org.microg.nlp.backend.apple, PID: 12257
01-28 16:46:18.251 12257 28801 E AndroidRuntime: java.lang.NullPointerException
01-28 16:46:18.251 12257 28801 E AndroidRuntime: at org.microg.nlp.backend.apple.BackendService$1.run(BackendService.java:79)
01-28 16:46:18.251 12257 28801 E AndroidRuntime: at java.lang.Thread.run(Thread.java:841)
I'm not sure how to reproduce, i just leave it on for some time. by checking the code it looks like onWiFIChange comes before onOpen which is the only case leads to "database == NULL"
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 in BackendService.java at the stack-trace locations on lines 57 and 79, then trace the onWiFIChange and onOpen callbacks and how they access database. Verify the callback ordering described in the issue and define completion as handling onWiFIChange before onOpen without a NullPointerException.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android, java
- Domain
- mobile
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100