Google Drive Android API ConnectionResult Error

Question

I'm making an app and I'm integrating the Google Drive Android API into it. I have a main activity then a fragment that opens that leads to google drive. However, when I try to sign in (it doesn't matter what gmail account, I've tried existing ones, creating new ones, whatever) I get ConnectionResult error code 17 SIGN_IN_FAILED. The app is authorized in the developer console and the Drive API is enabled. I don't know what else to do.

Here is the relevant code:

public class FileSharingFragment extends Fragment implements
    GoogleApiClient.ConnectionCallbacks, GoogleApiClient.OnConnectionFailedListener {

    @Override
    public void onCreate(Bundle savedInstanceState) {
        super.onCreate(savedInstanceState);

        if (mGoogleApiClient == null) {
            mGoogleApiClient = new GoogleApiClient.Builder(getActivity())
                .addApi(Drive.API)
                .addScope(Drive.SCOPE_FILE)
                .addConnectionCallbacks(this)
                .addOnConnectionFailedListener(this)
                .build();
        }
        mGoogleApiClient.connect();
    }

    @Override
public View onCreateView(LayoutInflater inflater, ViewGroup container,
                         Bundle savedInstanceState) {
    // Inflate the layout for this fragment
    View rootView = inflater.inflate(R.layout.fragment_file_sharing, container, false);
    users = (TextView) rootView.findViewById(R.id.users);
    getActivity().setTitle("Files");
    return rootView;
}

    @Override
public void onActivityResult(int requestCode, int resultCode,
                                Intent data) {
    super.onActivityResult(requestCode, resultCode, data);
    if (requestCode == REQUEST_CODE_RESOLUTION && resultCode == Activity.RESULT_OK) {
        mGoogleApiClient.connect();
    }
}

@Override
public void onConnectionFailed(ConnectionResult result) {
    Log.i(TAG, "GoogleApiClient connection failed: " + result.toString());
    if (!result.hasResolution()) {
        // show the localized error dialog.
        GooglePlayServicesUtil.getErrorDialog(result.getErrorCode(), getActivity(), 0).show();
        Log.i("file sharing fragment", "error code " + result.getErrorCode());
        return;
    }
    try {
        result.startResolutionForResult(getActivity(), REQUEST_CODE_RESOLUTION);
    } catch (IntentSender.SendIntentException e) {
        Log.e(TAG, "Exception while starting resolution activity", e);
    }
}

And to call it from the main activity I use

Fragment fragment = FileSharingFragment.newInstance();
FragmentManager fragmentManager = getFragmentManager();
        fragmentManager.beginTransaction().replace(R.id.content_frame, fragment).commit();

I cannot for the life of me figure out why it won't let me sign in.

Have you followed all the steps properly given [here](https://developers.google.com/drive/android/auth#generate_the_signing_certificate_fingerprint_and_register_your_application)? — Exception, Apr 17 '15 at 04:04
Go through [this answer](http://stackoverflow.com/questions/21280794/error-connectionresultstatuscode-internal-error-resolution-null#22738951). — Exception, Apr 17 '15 at 04:08

seanpj · Answer 1 · 2015-05-26T02:00:24.000

1

You probably know by now that your Developers Console needs 3 things:

1/ SHA1 of yout APK
2/ your package name
3/ your email/product name in the Consent Screen

Assuming everything is OK there, here's the last-resort double-check I use often:
- open (unzip) your xxxx.APK using unzipper (like 7zip), find CERT.RSA.
- run 'keytool -printcert -file .........\CERT.RSA'
Go back to the console and compare the SHA1's again.

Good Luck

edited May 26 '15 at 02:00

answered May 26 '15 at 01:23

seanpj

6,735
2
33
54

BTW, if you're on Android Studio, you may try this [DEMO](https://github.com/seanpjanson/GDAADemo), specifically step through [this gauntlet](https://github.com/seanpjanson/GDAADemo/blob/master/src/main/java/com/andyscan/gdrtdemo/MainActivity.java#L90) to see if it gets you anywhere – seanpj May 26 '15 at 21:07

score 1 · Answer 2 · answered Oct 02 '15 at 03:29

It might seem obvious but if you've entered your fingerprint on the developer console and set up your API there and are still getting SIGN_IN_FAILED make sure you are actually using the signed APK!

It's too easy to run installDebug from Gradle and forget. I usually set it up and go through the menus (Build > Generate Signed APK...) in Android Studio when I'm working with Google SDK's

score 0 · Answer 3 · answered May 26 '15 at 00:44

0

Over the Google Developers Console go to API & Auth -> Credentials and check the Package name is exactly the same that your Application Package name.

answered May 26 '15 at 00:44

Oscar Goenaga

1

score 0 · Answer 4 · answered Oct 09 '15 at 17:23

0

Make sure that you have generated an OAuth 2.0 Client ID as opposed to a normal API key

According to Google docs for youtube API - Your application must send an OAuth 2.0 token with any request that accesses private user data

answered Oct 09 '15 at 17:23

killianke

423
5
9

score 0 · Answer 5 · answered Oct 15 '17 at 19:33

0

Try uninstalling the app and starting the debug process all over (if you are using the debug.keystore.

answered Oct 15 '17 at 19:33

CoffeJunky

1,087
1
12
15

Google Drive Android API ConnectionResult Error

5 Answers5

Linked