I hit the same exception. From reading about SQLite it appears to be
creating separate database connections from two different threads can lead
to this. I'm not sure if that's the case, but from the previous poster
talking about posting the events at a later time I could see that might be.
Well, after another user apparently had 6 crashes in 2 minutes from
GoogleAnalyticsTracker.trackEvent() right when launching my app, I've
updated my app to wrap all Google Analytics calls in try-catch blocks
to quench the symptoms. Even though the crash reports were rare, this
seems to be the
I did the same, wrap all analytics calls in a try/catch block,
Mark
On Mon, Jan 3, 2011 at 3:39 AM, blindfold seeingwithso...@gmail.com wrote:
Well, after another user apparently had 6 crashes in 2 minutes from
GoogleAnalyticsTracker.trackEvent() right when launching my app, I've
updated my
A question - what version of the analytics sdk are you using..? There was a
new flavour released recently which said it fixed many of the bugs...
--
You received this message because you are subscribed to the Google
Groups Android Developers group.
To post to this group, send email to
anyone else getting this?
I have recently received several crash reports caused by Google
Analytics (version 1.1), such as
java.lang.IllegalStateException: no transaction pending at
android.database.sqlite.SQLiteDatabase.endTransaction(SQLiteDatabase.java:
480) at
You could stick a try/catch block in, but I doubt it would catch *most* of
the bugs. Remember that your request for a track simply gets added to the
database at that point and then some time later the dispatcher picks
requests up from the database and sends them (although if you ask it to
You may be right, although the crash reports that I have all suggest
that they were triggered from direct calls to
GoogleAnalyticsTracker.trackEvent() in my code leading to
java.lang.IllegalStateException: no transaction pending. Judiciously
sprinkling try-catch blocks is a great way to further
Looking in the analytics source after you've called trackEvent(), I suspect
that error is coming out when it is using a database transaction to insert
the event into the database. Once inserted, it calls endTransaction as well
as setTransactionSuccessful. Both of these do this check:
if
Hmm, I have only one global tracker object that I create in the
onCreate() of my main activity, and with a regular dispatch interval
through the format tracker.start(UA-12345-0, nseconds, this), so I'd
say that it all works from one alive thread. However, in one pair of
crash logs the first
9 matches
Mail list logo
