Android App Crashing: Google Drive SDK Integration Issue

Other Questions Google drive
1

I’m working on an Android app that uses the Google Drive SDK. I’ve followed an example I found online, but I’m running into a problem when I launch the app. It crashes immediately with a VerifyError.

Here’s a snippet of my main activity:

public class DriveIntegrationActivity extends Activity {
    private static final int SELECT_ACCOUNT = 1;
    private static String userAccount;
    private static int AUTH_REQUEST = 2;
    private Button connectButton;
    private Context context = this;
    private Activity activity = this;

    @Override
    protected void onCreate(Bundle savedInstanceState) {
        super.onCreate(savedInstanceState);
        setContentView(R.layout.activity_main);

        connectButton = findViewById(R.id.connect_button);
        connectButton.setOnClickListener(v -> selectAccount());
    }

    private void selectAccount() {
        Intent intent = AccountPicker.newChooseAccountIntent(null, null, 
            new String[]{"com.google"}, false, null, null, null, null);
        startActivityForResult(intent, SELECT_ACCOUNT);
    }

    // ... other methods for authentication and file listing
}

I’ve included the necessary permissions in my manifest:

<uses-permission android:name="android.permission.GET_ACCOUNTS" />

When I run the app, I get this error in LogCat:

FATAL EXCEPTION: main
java.lang.VerifyError: com/myapp/driveintegration/DriveIntegrationActivity
    at java.lang.Class.newInstanceImpl(Native Method)
    at java.lang.Class.newInstance(Class.java:1319)
    at android.app.Instrumentation.newActivity(Instrumentation.java:1053)
    at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:1974)
    // ... more stack trace

What could be causing this VerifyError? Any ideas on how to fix it?

2

I’ve dealt with this exact problem before. The VerifyError is usually a sign of bytecode incompatibility, often caused by mismatched library versions.

Make sure you are using the latest version of the Google Drive SDK and that it aligns with your app’s target SDK. Sometimes older versions can trigger these errors.

Also, carefully review your Gradle dependencies. Mixing different versions of Google Play Services libraries can lead to conflicts that result in a VerifyError.

Check your Proguard configuration as well to ensure it isn’t obfuscating or removing essential Google Drive classes. If the problem persists, consider switching to the Google Drive REST API for a more reliable integration.

3

I encountered a similar issue when integrating Google Drive SDK. The VerifyError often stems from incompatible bytecode, typically due to version mismatches. Ensure your Google Play Services and Drive SDK versions are compatible with your target Android SDK. Also, verify that you’ve properly initialized the Google Drive API client in your onCreate() method. Sometimes, the issue lies in the build process - try cleaning and rebuilding your project. If the problem persists, consider using the newer Google Drive REST API instead of the SDK, as it’s more stable and easier to implement in my experience.

4

hey there, had similar issue. make sure ur using latest google play services in gradle. also, check if ur proguard rules r messing with google drive classes. sometimes older versions cause verify errors. double-check ur dependencies and update em. good luck!