🔥 Fire Analytics : An extension to add Firebase Analytics to your apps

[UnknownBeast (Beast)]

How to implement the Firebase Analytic extension in my app

In the community I have found an extension that allows to implement Firebase Analytic in apps, but there is no tutorial on how to link the google Analytic account. If anyone knows the correct use of said extension, I appreciate your help. The extension is this: Firebase Analytics

For reference of users

[Avijit (Avijit Das)]

Going to import in my project.
By the way after create any event how many time take to show in Firebase ?

[UnknownBeast (Beast)]

@Avijit

By the way after create any event how many time take to show in Firebase ?

I tried first time and it took 1 day to display

[charlesaccount (CharlesKoder93)]

Hi UB,

This is really cool, I’m interested in tracking my project with FB, but when I build with the latest version of Kodular, it is not able to build aabs. I tested even with the fire.aia you released on the other thread with how to use extension. This is the error log I get:
Kodular is unable to compile this project.
The compiler error output was
________Preparing application icon
________Creating animation xml
________Creating fragment xml
________Creating listview xml in res/layout/…
________Creating listview xml in res/layout-v21/…
________Creating xml in res/drawable/…
________Creating splash png in res/drawable/…
________Creating colors xml
________Creating styles xml
________Creating drawables xml v21
________Checking for firebase
________________Firebase components found.
________________Firebase config file error.
.
Edit:
I did test on my actual project and added the google services.json etc, with same error.

[dora_paz (Dora)]

Error comes because you didn’t add google-services.json

[charlesaccount (CharlesKoder93)]

I realized that may pop up, so I edited my op under my log that I have already done that, and my original project which does have a firebase project gets stuck at 85% building always still.

[dora_paz (Dora)]

Still same error ? Firebase config file error ? If yes

1. Make sure that google-services.json is in assets.
2. Make sure it doesn’t have a number, like google-services(1).json.
3. The package name of your app, and the package name you provided to firebase to download “google-services.json” MUST be the same
4. and finally check if firebase url is missing from json

Unable to generate apk because of Firebase, Firebase config file error

To be honest I have no knowledge of Firebase. But by looking at one of the json files that were lying around here on my PC, I saw that one line was missing in both cases "firebase_url": "https://your-projekt-id.firebaseio.com", if it is the right/correct one I have no idea… "project_info": { "project_number": "123456789", "firebase_url": "https://your-projekt-id.firebaseio.com", "project_id": "your-projekt-id", "storage_bucket": "your-projekt-id.appspot.com"

[charlesaccount (CharlesKoder93)]

Thank you, I will check these things

[charlesaccount (CharlesKoder93)]

I went through your check, the firebase url I was missing, thanks again.

I’m still a bit “wet behind the ears” with Firebase, but I checked my Real-time Database and app settings and ids were matching, checked my google-services.json, rebuilt my app and unfortunately having an error still, but the log is different. However, when I remove the ext. it builds again:
Kodular is unable to compile this project.
The compiler error output was
________Preparing application icon
________Creating animation xml
________Creating fragment xml
________Creating listview xml in res/layout/…
________Creating listview xml in res/layout-v21/…
________Creating xml in res/drawable/…
________Creating splash png in res/drawable/…
________Creating colors xml
________Creating styles xml
________Creating drawables xml v21
________Checking for firebase
________________Firebase components found.
________________Firebase config file successfully added.
________Creating provider_path xml
________Creating network_security_config xml
________Generating adaptive icon file
________Generating round adaptive icon file
________Generating adaptive icon background file
________Generating manifest file
________Attaching native libraries
________Attaching Android Archive (AAR) libraries
________Attaching component assets
________Invoking AAPT
AAPT2 compile time: 0.423 seconds
AAPT2 link time: 1.274 seconds
________Compiling source files
(compiling ************************************/Screen1.yail to ***********************************************.Screen1)
(compiling /tmp/runtime363568459752595713.scm to com.google.youngandroid.runtime)
Kawa compile time: 3.695 seconds
________Invoking DX
DX time: 37.04 seconds
___________Creating structure
___________Extracting protobuf resources
________Running bundletool
.

I could be missing something obvious, but checking the log, not sure. (*Note I intentionally obfuscated just my project name and such).

[Jihed]

@UnknownBeast
It already worked but only the first time and the rest of the times it didn’t work
Even though I have a google file in the media
What is the cause of the problem and is there a solution?

[Hanuman_Singh]

What is use of Tag and Value in Log block?

[Hanuman_Singh]

Hi,
I wanted to know if Fire Analytics works in Companion…
Please tell

[UnknownMan541 (Shubhanshu Jaiswal)]

Developer left KODular

[Jihed]

I used this extension and my app crashed because of it !!!

[Connectappcreator (Connect App)]

extension is not updated, causing crash.

[Jubayer_Ahmed]

This will work?

[UnknownBeast (Beast)]

well, I no more gurantee working of my firebase extensions because, all of them are built on latest sdk, whereas kodular one’s have bit too old sdk (That may cause conflicts)

[Jubayer_Ahmed]

An update from Kodular Staff read this

Big Update

As stated above, we are working on a huge update to address most of the issues and make sure that Kodular keeps running for more years.
At a glance, this update will bring Target SDK 32, and will (finally) integrate the new Android file system, so all related bugs to that problem should be solved. It will also include new features and minor improvements as well.
But it will also finally deprecate Google Admob components, as they will no longer be available, even for existing apps. Thus, migration to Google Ad Manager shall be mandatory by that date if you want your app to target Android 12.

We are aiming to launch this update on the 26th of June 2022. We will keep the community up-to-date if this changes at any point.

[UnknownBeast (Beast)]

@Jubayer_Ahmed

At a glance, this update will bring Target SDK 32, and will (finally) integrate the new Android file system, so all related bugs to that problem should be solved. It will also include new features and minor improvements as well.
But it will also finally deprecate Google Admob components, as they will no longer be available, even for existing apps. Thus, migration to Google Ad Manager shall be mandatory by that date if you want your app to target Android 12.

My reply states the old sdk to be sdk present in firebase components, not target sdk, etc stuff…