linkedin / linkedin/test-butler

java.lang.NoClassDefFoundError: android.provider.Settings$Global

Open
#81 8 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Java
Stars
1k
Forks
94
PR merge metrics
No merged PRs in 30d

Description

test-butler 1.4.0 crashes on a emulator with SDK level 15 with:

```
I/ActivityManager( 1259): Start proc com.linkedin.android.testbutler for service com.linkedin.android.testbutler/.ButlerService: pid=1784 uid=1000 gids={1015, 3002, 3001, 3003}
E/AndroidRuntime( 1784): FATAL EXCEPTION: main
E/AndroidRuntime( 1784): java.lang.NoClassDefFoundError: android.provider.Settings$Global
E/AndroidRuntime( 1784): at com.linkedin.android.testbutler.AlwaysFinishActivitiesChanger.getAlwaysFinishActivitiesState(AlwaysFinishActivitiesChanger.java:62)
E/AndroidRuntime( 1784): at com.linkedin.android.testbutler.AlwaysFinishActivitiesChanger.saveAlwaysFinishActivitiesState(AlwaysFinishActivitiesChanger.java:39)
E/AndroidRuntime( 1784): at com.linkedin.android.testbutler.ButlerService.onCreate(ButlerService.java:153)
E/AndroidRuntime( 1784): at android.app.ActivityThread.handleCreateService(ActivityThread.java:2253)
E/AndroidRuntime( 1784): at android.app.ActivityThread.access$1600(ActivityThread.java:123)
E/AndroidRuntime( 1784): at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1201)
E/AndroidRuntime( 1784): at android.os.Handler.dispatchMessage(Handler.java:99)
E/AndroidRuntime( 1784): at android.os.Looper.loop(Looper.java:137)
E/AndroidRuntime( 1784): at android.app.ActivityThread.main(ActivityThread.java:4424)
E/AndroidRuntime( 1784): at java.lang.reflect.Method.invokeNative(Native Method)
E/AndroidRuntime( 1784): at java.lang.reflect.Method.invoke(Method.java:511)
E/AndroidRuntime( 1784): at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:784)
E/AndroidRuntime( 1784): at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:551)
E/AndroidRuntime( 1784): at dalvik.system.NativeStart.main(Native Method)

```

Contributor guide

Open the contributing guide

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 with AlwaysFinishActivitiesChanger.java at line 62 and the ButlerService.onCreate path shown in the stack trace. Reproduce the crash on an Android SDK 15 emulator and inspect the failing Settings.Global lookup. Done means test-butler starts without NoClassDefFoundError on that emulator.

Written by the indexing model from the issue text.

Assessment

Tech stack
android, java
Domain
mobile-dev, testing
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.