I have installed the fabric,integrated jar files and API key.I am always on "https://www.fabric.io/onboard" instead of " https://fabric.io/dashboard".Unable to see the crash report.I have used correct email Id.
Please help,Thanks in advance.
you can see the app here
https://fabric.io/home
and please wait some time to get updated .also double check in your app below line is enabled or not
Fabric.with(this, new Crashlytics());
also check these from the documentation
If you're getting started with Crashlytics for Android,
Make sure our SDK line is after all other 3rd-party SDKs Force a crash
and then relaunch the app. If you're using our
Crashlytics.getInstance().crash() method for testing purposes, make
sure it's not in the onCreate method of your launch Activity
Related
I am trying to implement App invites in my app. Here's the java code that I am using :
Intent intent = new AppInviteInvitation.IntentBuilder(getString(R.string.invitation_title))
.build();
startActivityForResult(intent, Constants.REQUEST_CODE_INVITE);
But, as soon as I am clicking on the button which executes this code, a dialog pops up saying 'Unfortunately, Google Play Services has stopped'.
I have tried disabling, uninstalling and installing google play services again, and even restarting the phone, but no use.
No Exception is shown in android studio logs, so I am not able to figure out the problem is.
Please help.
There are a few issues here, and I'd also you to validate values.
getString requires resources. Assuming you are calling this from in an activity, you need to call
getResources().getString(R.....). You are likely getting null
returned which would result in an exception.
Although there is only 1 required parameter, you should fill out a few more to make sure you have a reasonable invitation, specifically setMessage(). Also, you can use setAccount() if you know the account, otherwise it will prompt.
I would also validate the input values. For example, log the string value you get for R.string.invitation_title to make sure you have set this correctly before you call the builder.
I was making a silly mistake which was leading to the error.
I was not initializing the GoogleApiClient before sending out the intent. Don't know how I missed it.
Here's the code that I was missing :
GoogleApiClient mGoogleApiClient = new GoogleApiClient.Builder(this)
.addApi(AppInvite.API)
.enableAutoManage(this, this)
.build();
Hope it helps future visitors to this page.
I am trying to enable Saved Game in my Android game. However, I find that if I call
builder.addApi(Drive.API);
builder.addScope(Drive.SCOPE_APPFOLDER);
the "Select Account" dialog doesn't even shown at all, and I cannot therefore sign in.
Uncommenting both lines and everything works fine (sign in, leaderboard, achievement) except Save Game. Trying to get a Snapshot gives me the following error
01-11 23:30:14.549 18072-18488/? E/Evaderīš Must include Drive.SCOPE_APPFOLDER to use snapshots!
java.lang.IllegalStateException: Must include Drive.SCOPE_APPFOLDER to use snapshots!
Is this deprecated? This is the method recommended on https://developers.google.com/games/services/android/savedgames
I am working with LibGDX and the BaseGameUtils if that's relevant
If the code you included in your question is accurate, the problem is in how you are calling the Builder class.
The client is constructed using a builder pattern, so you need to update the return value of the previous call when creating the builder instance, such as: (notice there is only one semi-colon).
mGoogleApiClient = new GoogleApiClient.Builder(this)
.addApi(Games.API).addScope(Games.SCOPE_GAMES)
.addApi(Drive.API).addScope(Drive.SCOPE_APPFOLDER)
.build();
The problem wasn't with the code whatsoever. It was the phone(test device).
I tested on another device and it worked flawlessly.
I updated uninstalled Google Play Store and Google Play Services updates, and re-installed them, and everything worked.
TLDR - Test on multiple devices. I'm not exactly sure why that happened on my device for my game only, but after performing the above, everything works.
Thanks Clayton Wilkinson
Unable to receive crash reports on my Test flight account even though application gets crashed.
I integrated the SDK in my application. I did following steps -
1. Integrated SDK in code
2. Used proper Application ID
3. Started session using TestFlight.startSession();
4. Called TestFlight.sendCrash(121213, "XXX", "YYY"); method
4. Ended session using TestFlight.endSession(); in one of my destroy() method.
Let me know if I am doing anything wrong or missing anything.
Thanks in advance, your answers will be much appropriated.
Crash sessions should be sent back to TestFlight automatically. There is no need to specify startSession, sendCrash, and endSession. Please contact TestFlight support here (http://help.testflightapp.com/customer/portal/emails/new) so we can further investigate. Please include the URL to the build's permissions page in the email.
Thanks,
Justin (TestFlight Support)
I am new to phonegap and I want to implement pushwoosh notification services but I cant get it right. Every time I call the registerPushwoosh() function I get this error.
I am using the SDK Sample Project -> Android Phonegap.
every time getting this error.
how to fix ["failed to register ","Device does not have package com.google.android.gsf"]
here is image link ERROR AND DIrectory
You need to use Emulator with a Google API.
I am installing google analytics and when i write the line of code:
tracker.start(UA-..., 10)
Eclipse gives a warning that start method is deprecated. Anyone has done this recently? Are there new set of instructions on how to install google analytics? I am unable to find it.
#Valeh that link still has the depreciated code in there.
#NoviceMe I had the same issue, you may have found it already but if it helps someone else. Its not going to brake your code but have a look at this page under the heading 'Depreciations'
http://analytics.blogspot.com/2011/08/new-google-analytics-sdk-for-android.html
it says:
We are deprecating the start and stop methods in favor of the startNewSession and stopSession. The existing methods will continue to be in the library, so your applications will still work when you upgrade, but we highlight recommend you move to these new methods.
Previously where you had:
tracker.start("UA-YOUR-GA-ACC-NUM", intCallPeriod, getApplication());
tracker.stop();
You will have:
tracker.startNewSession("UA-YOUR-GA-ACC-NUM", intCallPeriod, getApplication());
tracker.stopSession();
hope it helps.