Quickstart-ios: <FIRAnalytics/ERROR> Transaction failed

[myflashlab]

In my app, I am calling [FIRApp configure]; not exactly in application didFinishLaunchingWithOptions but early enough before anything else starts.

And when I look at the xcode console, it says:

<Notice>: <FIRAnalytics/INFO> Firebase Analytics v.3200000 started
<Notice>: <FIRAnalytics/INFO> To enable debug logging set the following application argument: -FIRAnalyticsDebugEnabled (see http://goo.gl/Y0Yjwu)
<Notice>: <FIRAnalytics/INFO> Successfully created Firebase Analytics App Delegate Proxy automatically. To disable the proxy, set the flag FirebaseAppDelegateProxyEnabled to NO in the Info.plist
<Notice>: <FIRAnalytics/INFO> Firebase Analytics enabled
<Notice>: Sandbox: myappname(2327) deny(1) file-write-create /private/var/mobile/Containers/Bundle/Application/FIREBASE_LAST_TIMESTAMP

Which seems good, accept for the last line which I don't understand what it's about!

The actual problem is the following error message which happens as soon as I click on a test Admob banner. When my app switches to Safari browser, Firebase throws this error. but this does not crash the app at all. everything seems normal.

<Error>: <FIRAnalytics/ERROR> Data loss. Cannot record raw event. Error: Error Domain=com.google.gmp.measurement.ErrorDomain Code=3 "Database operation "execute statement" failed with sqlite code 20 and error message "could not convert floating point value to integer without loss of data."" UserInfo={FIRAMonitorContext=execute statement,20,A,3, NSLocalizedDescription=Database operation "execute statement" failed with sqlite code 20 and error message "could not convert floating point value to integer without loss of data."}
<Error>: <FIRAnalytics/ERROR> Transaction failed

Now, what this problem leads? in my Firebase console, I am not seeing reports! we have created two projects in our Firebase console, one for our Android app and another one for the iOS. We are able to see the analytic on the Android side but the iOS side still shows 0 monthly active users.

Please give us an advice on what could be the problem?

[FIRApp configure]; This method should be called after the app is launched and before using Firebase services.

NOTE: Because of some reasons, we can NOT call [FIRApp configure]; from application didFinishLaunchingWithOptions but we do call it a bit later. If this is the problem, which I don't think it is because if it was, the console logs should have said so, what solution do we have?

Thanks a lot in advanced and we can't wait to start developing using Firebase. It's just so awesome.

[myflashlab]

NOTE1: I should add that the app we are testing, is not uploaded to itunesConnect yet... I hope That's not the reason, is it?

NOTE2: I know the reports would take 24 hours to reflect on the Firebase console. I did wait more than 24 hours.

[baolocdo]

Thanks for reporting in details. The last line
<Notice>: Sandbox: myappname(2327) deny(1) file-write-create /private/var/mobile/Containers/Bundle/Application/FIREBASE_LAST_TIMESTAMP
is a known bug and we are on it.
Can you please turn on debug using application argument -FIRAnalyticsDebugEnabled and provide the debug log?

[myflashlab]

Thanks for getting back to us on this. About turning on the
-FIRAnalyticsDebugEnabled
parameter, unfortunately we can't do that because we are compiling the
project in Adobe Air and that debug parameter can run on xCode only (if I'm
not wrong) do you have any other advice?

[baolocdo]

I don't know much about Adobe Air to advise. However, we think we found the problem and will try to produce the fix soon. Thanks for reporting.

[myflashlab]

cool, waiting for the new release. as soon as it's released, we will test it and let you know the results.

[myflashlab]

I just updated to iOS V3.6.0 and we are still having the very same problem. Let me know how I can help you in finding and fixing the problem on your side.

[baolocdo]

Due to some technical issues, we have not pushed the fix for this bug out yet. Sorry for the late response.

[baolocdo]

Update: The bug regarding this
<Notice>: Sandbox: myappname(2327) deny(1) file-write-create /private/var/mobile/Containers/Bundle/Application/FIREBASE_LAST_TIMESTAMP
was fixed and should not show up in the latest release of Firebase Analytics.
However, regarding Adobe Air support, we still have not released the fix yet due to some technical issues. Thanks for reporting.

[myflashlab]

@baolocdo Thanks for your update. We are totally looking forward to the other fix. You know, the whole Adobe AIR community is currently dependent on us to have this feature of the Firebase project available to them along with the other pieces. https://github.com/myflashlab/Firebase-ANE

I'm sure a lot AIR developers will be happy as soon as you fix the <FIRAnalytics/ERROR> Data loss issue :) Thanks.

[TimKoppers]

@baolocdo Thanks for the headsup. Would be great if you guys can fix this error, I'm depending on it to integrate Firebase analytics in our game (iOS and Android).

Thanks a lot!

[mrgoonie]

Hi @baolocdo @myflashlab , just curious, do you guys have any ideas regarding estimating the release date of the fix?

My app is about to release soon & this is our final step. I'm on fire, mates 😃

Thanks,

[baolocdo]

Unfortunately, we don't have an estimate fix for this bug. We have to prioritize other bug fixes and features but we do have an eye on this bug and we are trying to fix it as soon as we can. Sorry for keeping you waiting.

[mrgoonie]

Thanks for the notice @baolocdo . Please keep us posted! Really appreciated for your team's effort, keep going strong!

[adammendoza]

I'm getting this error too. Are there any work arounds?

[baolocdo]

Currently, there is no work around. We have the fix and it will probably be released in the next release.

[myflashlab]

@baolocdo Awesome :) we are eagerly waiting for that. If that's happening in the next updated release, we will test it imminently and let you know the results.

[ambient-sky]

Thanks @baolocdo, we're eagerly awaiting this, too, as we're about to start a big AdWords campaign and are only able to collect attribution data on Android without this fix. We really want to be able to collect attributation data for iOS, too. We'd be happy to beta test and confirm your fix.

[baolocdo]

Good news: The fix has just been released in Firebase Analytics 3.7.0. Please upgrade to the latest version and let us know if it fixes this error. Thanks for reporting!

[myflashlab]

Awesome @baolocdo I can confirm that it works fine now :)

[baolocdo]

Great! Thanks for confirming that it works!