OneSignal AIX Compiles via Fast CLI but Fails in a Project error [ReadBuildInfo] Task errored

[Ibrahim_Jamar]

Hello,

I am working on a custom OneSignal extension. I have arranged and cleaned up the Java code, and I am compiling it using Fast CLI 🏃‍♂️ Fast : An Efficient Way to Build & Publish Extensions] 🏃‍♂️ Fast : An Efficient Way to Build & Publish Extensions . The .aix file builds successfully without any errors when running fast build.

However, after importing the generated extension into a testing project, the project fails to compile/export the APK, and I get the following output

[ReadBuildInfo] Starting Task
[ReadBuildInfo] Task errored

The extension itself has no assets, all classes are included in the code, and it compiles perfectly using Fast CLI. I suspect the issue may be related to project-level integration, metadata parsing, or platform-specific build constraints, but I am unable to identify the root cause.

Has anyone faced similar issues with large or complex extensions built via Fast CLI? @JEWEL @Taifun @vknow360 @Still-learning and all Extension developer’s Any guidance on resolving this project compilation error would be appreciated.

Thank you.

[Still-learning]

Yes of course i met. Mostly this problem occurs with initialize event. Checkup how do you initialise your extension.

To cross check up just compile the extension without initi and check up with apk it wont throw such error

[RaYzZz (Gianluca Franco)]

I had Ibrahim send me the extension and I think I found the problem,

(always assuming that I’m not an expert in extensions)

I noticed that the folder structure was

com.jamar.onesignalextension
| - files
| | - component_build_infos.json
| | - AndroidRuntime.jar
|   | - com
|     | - jamar
|       | - onesignalextension
|         | classes....
| - components.json
| - classes.jar

The type in component_build_infos.json was pointing to com.jamar.onesignalextension.OneSignalExtension.
I simply corrected it to com.jamar.onesignalextension, thus matching the folder structure.
And also renamed the app to com.jamar.onesignalextension.aix
Now the app builds correctly.

[Ibrahim_Jamar]

@RaYzZz

I simply corrected it

Awesome,

@RaYzZz

And also renamed the app to com.jamar.onesignalextension.aix

?? do you mean the app should be named like this anytime the aix is used? Though here it built the app normaly.

[RaYzZz (Gianluca Franco)]

Unfortunately I can’t give you much information about it,

@RaYzZz

(always assuming that I’m not an expert in extensions)

but I’ve noticed that FAST usually creates extensions by repeating the name, in this case I think

@Ibrahim_Jamar

@JEWEL @Taifun @vknow360 @Still-learning

can explain it better to us

[Ibrahim_Jamar]

@RaYzZz

FAST usually creates extensions by repeating the name

Exactly see below my directory path

C:\Users\3PIN\one-signal-extension\src\com\jamar\onesignalextension\onesignalextension

So if i remove/delete the last folder \onesignalextension\onesignalextension as

C:\Users\3PIN\one-signal-extension\src\com\jamar\onesignalextension

Do you think it will work? Anyway i will give it a try when am free

[Still-learning]

package name must be same as with the src. do not change it, else your extension be hard to read by the app

[Ibrahim_Jamar]

@Ibrahim_Jamar

C:\Users\3PIN\one-signal-extension\src\com\jamar\onesignalextension\onesignalextension

But this path is created by Fast itself

[Still-learning]

then in the package name just add the folder name,