App Crash

[zigzag-way]

Since I integrated this plugin I began recieving lots of crashes like this one:

Fatal Exception: java.lang.RuntimeException
Unable to resume activity {mobi.appcoins/mobi.appcoins.AppCoins}: java.lang.RuntimeException: Failure delivering result ResultInfo{who=null, request=0, result=0, data=null} to activity {mobi.appcoins/mobi.appcoins.AppCoins}: java.lang.NullPointerException
 raw
android.app.ActivityThread.performResumeActivity (ActivityThread.java:2458)
android.app.ActivityThread.handleResumeActivity (ActivityThread.java:2486)
android.app.ActivityThread.handleLaunchActivity (ActivityThread.java:2000)
android.app.ActivityThread.access$600 (ActivityThread.java:128)
android.app.ActivityThread$H.handleMessage (ActivityThread.java:1161)
android.os.Looper.loop (Looper.java:137)
android.app.ActivityThread.main (ActivityThread.java:4517)
java.lang.reflect.Method.invokeNative (Method.java)
dalvik.system.NativeStart.main (NativeStart.java)

[EddyVerbruggen]

That's not a really useful stacktrace unfortunately. Can you share a stripped down version of your app (or a new cordova cli one) which reproduces this problem so I can take a look?

[zigzag-way]

http://crashes.to/s/8cc21611288 - here are all the details from CrashLytics

[zigzag-way]

I can not reproduce it, but see in production on a certain amount of users thx to CrashLytics

[zigzag-way]

Any ideas? At this moment this plugins is the most crashable part of my app... May be I`m using it wrong?

[zigzag-way]

More and more crashes - http://crashes.to/s/8cc21611288

[EddyVerbruggen]

Thanks for those Crashlytics details, really helpful!

Can you try a new version from master to see if this fixes the issues?

[zigzag-way]

Yes, I will integrate it on the next version within next 2-3 hours

[zigzag-way]

Ok. No lets check for the next few days to see the stats

[zigzag-way]

As I can see - you`ve fixed it!
But ))) It seems we got a new issue
http://crashes.to/s/0b6b00f47c8

[zigzag-way]

Eddy? Did you check the last\new issue (http://crashes.to/s/0b6b00f47c8)?

[zigzag-way]

More crashes in the new app: http://crashes.to/s/16da04e3dae and http://crashes.to/s/d2d8cad7e4a

[zigzag-way]

http://crashes.to/s/16da04e3dae

[zigzag-way]

http://crashes.to/s/51c3798b11b - I thought this one should leave in the last update ((( but it`s still there

[sammugg]

@zigzag-way,

Have you installed the app from GitHub or from the npm registry? If you installed from npm, please try out the latest code from GitHub! The usage has changed a bit, but I hope it clears up the issue you've been having.

[zigzag-way]

Yes. I did. From git.

[sammugg]

@zigzag-way,

Can you get some more info by USB debugging the app on a device? I'm want to be sure that your options are making it into GooglePlus.java.

Side note, if the issue is what I think it is, @pranay-mathur is running into the same problem you are. He started issue thread #199.

If it's the same issue, let's move this conversation over to that thread.

[zigzag-way]

Can you get some more info by USB debugging the app on a device? - no, i cant because i dont face this issue. but my users do.

I use this options to initialize:

                        $window.plugins.googleplus.trySilentLogin(
                            { offline: 'true', webApiKey: WEB_API_KEY },
                            function (user) {
                                console.info('Silent Login: ' + JSON.stringify(user));
                                serverAuth(user);
                            },
                            function (msg) {
                                $ionicLoading.hide();
                                console.error('Silent Login error: ' + msg);
                            }
                        );

[sammugg]

@zigzag-way,

First, webApiKey is no longer a valid option. It has been replaced with webClientId. I merged a significant PR the other day that updated the Android side to use Google Sign-In and refactored plugin usage. The current documentation is up to date with those changes.

Second, after looking at my code and your crashlytics page again, I noticed that Line 235 in the latest code is part of a Javadoc comment (I've been at work all day, so I didn't get a chance to check that until now). So, that error, to the best of my knowledge, has two possible causes:

1. The user has not updated the application, but it's still polling the same analytics system, so the same error shows up.
2. You're not actually running the latest version of the plugin.

In order for us to be sure that the second case is not the problem, could you please reinstall the plugin using the second (GitHub URL) method found in the README?

[zigzag-way]

You're not actually running the latest version of the plugin. - How can I check that I`m running the latest version?

[zigzag-way]

1. Its definetely not the reason because I track the version and know in which version the issue happened.

[sammugg]

Version: Go into the plugin directory and open plugin.xml.
The version that gets pulled from npm (plugin add cordova-plugin-googleplus) is 4.0.8. The version that gets pulled from github (plugin add https://github.com/EddyVerbruggen/cordova-plugin-googleplus) is 4.0.9.

If you are running 4.0.8, I recommend that you update to 4.0.9. The usage is different, and the information you get back is purely directed at authentication and identity.

[zigzag-way]

Thx, its 4.0.8 now. I`ll update it soon.

[zigzag-way]

Hm... I`ve update the plugin from git:
Now plugin.xml shows 4.0.9
But package.json show 4.0.8
Which one is correct?

[zigzag-way]

After the update the new issue came out:
http://crashes.to/s/5c55ff7bb1d

[sammugg]

@zigzag-way,

Package.json/Plugin.xml version: That was my bad. I forgot to update the version in package.json when I updated plugin.xml. I just pushed that today (but it's not something that would break anything; just an inconsistency; whoops).

Hmmmm so that crash is at line 275 of GooglePlus.java, which is part of the following if statement:

274: if (mGoogleApiClient == null) {
275:     savedCallbackContext.error("GoogleApiClient was never initialized");
276:     return;
277: }

This tells me two things: The GoogleApiClient was null, but then never got built (which shouldn't happen....), and that an error callback was not provided and/or saved.

Did you ever try removing your android platform entirely then readding it? If not, could you give that a go?

If that doesn't work, can you double check that you're passing in an error callback function?

Those are the only things I can think of right now....

P.S. I know removing the platform seems weird, but other people have done that and on reinstalling things were fixed. Technology's weird, right?

[zigzag-way]

Btw, I just tried to add it to another Cordova project that is build through Eclipse and it failed.
Description Resource Path Location Type
Auth cannot be resolved GooglePlus.java /src/nl/xservices/plugins line 181 Java Problem
Description Resource Path Location Type
The import com.google.android.gms.auth.api cannot be resolved GooglePlus.java /src/nl/xservices/plugins line 6 Java Problem

All imports
Description Resource Path Location Type
The import com.google.android.gms.auth.api cannot be resolved GooglePlus.java /AppCoins/src/nl/xservices/plugins line 6 Java Problem
failed.

Whats wrong? Before that I successfuly used previous version of the plugin

[sammugg]

Hmmm that error means the Auth api is not getting brought into the project at compile.

cordova build android should bring in the Auth api materials from the android sdk on its own. Make sure there aren't any build settings that you're missing.

[zigzag-way]

http://crashes.to/s/19494d28a81

What am I doing wrong? Why do I get this kind of issues?

[zigzag-way]

And here is another issue: http://crashes.to/s/4cf818b5a9a

[zigzag-way]

I`m using the plugin this way:

        window.plugins.googleplus.trySilentLogin(
            {}, //just client usage
            function (obj) {
                console.info('Silent Login: ' + JSON.stringify(obj));
            },
            function (msg) {
                console.error('error: ' + msg);
                window.plugins.googleplus.login(
                    {},
                    function (obj) {
                        console.info('Login: ' + JSON.stringify(obj));
                    },
                    function (msg) {
                        gaPlugin.trackEvent(null, null, "login", "g+ login error", "", 0);
                    }
                );
            }
        );

[sammugg]

Are you passing anything in to login when you call it? You should pass in the same variables to make sure the api client is being built as expected.

[zigzag-way]

Sorry, dont understand what you mean.
Btw, it`s only some % of users facing this issue.

[sammugg]

Oh sorry I didn't see googleplus.login in nested in the code snippet you posted.

My recommendation is that you use login and trySilentLogin separately.

i.e., on app start up, call trySilentLogin and handle the result of that. Then provide a button of some sort for the user to click when they are ready to log in to the application.

(I'm glad to hear it's only some % of users. That means that it could be an issue with their version of Android or Google Play services. I don't know much more than that.)

[zigzag-way]

One more error:
http://crashes.to/s/d6ab4561a41

May be this will help you to find the issue.

[zigzag-way]

May be this happens if there is no gpservices on the device?

[zigzag-way]

No more ideas? http://crashes.to/s/19494d28a81 - this is still my most frequent bug mostly affected by Android 4.X

[sammugg]

No other users of this plugin have reported this particular exception. My only suggestion is that you make sure all of your build tools and other SDK items are up to date. This plugin, and the Google sources it uses, are supposed to be compatible back to Android 2.3.

From the Android documentation:

Google Sign-In for Android has the following requirements:

• A compatible Android device that runs Android 2.3 or newer and includes the Google Play Store or an emulator with an AVD that runs the Google APIs platform based on Android 4.2.2 or newer and has Google Play Services version 9.2.1 or newer.
• The latest version of the Android SDK, including the SDK Tools component. The SDK is available from the Android SDK Manager in Android Studio.
• A project configured to compile against Android 2.3 (Gingerbread) or newer.
• The Google Play Services SDK:
  1. In Android Studio, select Tools > Android > SDK Manager.
  2. Scroll to the bottom of the package list and select Extras > Google Play services. The package is downloaded to your computer and installed in your SDK environment at android-sdk-folder/extras/google/google_play_services.