Linking library manifests

[Ventili]

Is your feature request related to a problem? Please describe.

Now I have to manually connect all the libraries. I would like to do this as easily as in Gradle.

Describe the solution you'd like

When the library is connected, all dependencies and the provider are also connected.

Describe alternatives you've considered

No response

Additional context

No response

[webmturn]

I am currently conducting a code quality review for this project. I won’t be working on this feature for now; I’ll start on it once the quality review is completed.

[webmturn]

You can describe the features you want in as much detail as possible. Implementing the full Gradle functionality is very difficult, and the complexity and risks are high. I can create a solution that covers the most common AAR scenarios, while keeping manual injection as an escape hatch.

[Ventili]

You decide which features to build and when to build them. I simply used the suggest feature.

В настоящее время я проверяю качество кода в этом проекте. Я пока не буду работать над этой функцией, займусь ею после проверки качества.

[Ventili]

Вы можете максимально подробно описать желаемые функции. Реализовать все возможности Gradle очень сложно, это сопряжено с большими трудностями и рисками. Я могу создать решение, которое будет охватывать наиболее распространенные сценарии использования AAR, при этом оставив возможность ручного внедрения.

As for functionality, I just want the libraries to work out of the box without any additional configuration, just like in Gradle (implementation), and the magic will happen.

[webmturn]

Вы можете максимально подробно описать желаемые функции. Реализовать все возможности Gradle очень сложно, это сопряжено с большими трудностями и рисками. Я могу создать решение, которое будет охватывать наиболее распространенные сценарии использования AAR, при этом оставив возможность ручного внедрения.

As for functionality, I just want the libraries to work out of the box without any additional configuration, just like in Gradle (implementation), and the magic will happen.

Bro, I've already implemented the feature you mentioned.

[Ventili]

Вы можете максимально подробно описать желаемые функции. Реализовать все возможности Gradle очень сложно, это сопряжено с большими трудностями и рисками. Я могу создать решение, которое будет охватывать наиболее распространенные сценарии использования AAR, при этом оставив возможность ручного внедрения.

As for functionality, I just want the libraries to work out of the box without any additional configuration, just like in Gradle (implementation), and the magic will happen.

Bro, I've already implemented the feature you mentioned.

Bro, you're awesome. I'll definitely test it out and give you feedback.

[xein666]

Bro.. I want to ask, why does FirebaseDB keep deleting itself? I mean, I'm making an app in beta 7, the app I made is connected to FirebaseDB. So when I open the library manager, FirebaseDB deletes itself, even though I didn't tamper with it, I just looked at or checked which local libraries are already active. Maybe some people who don't understand Compile errors will be confused about fixing the error, even though it's just FirebaseDB deleting itself. Hopefully, you understand what I mean, my English is bad ;)
and another thing in beta 7 it feels heavy when opening the application like it's lagging, if the previous beta 6.3 that you made feels light and responsive (without lag)

[webmturn]

Bro.. I want to ask, why does FirebaseDB keep deleting itself? I mean, I'm making an app in beta 7, the app I made is connected to FirebaseDB. So when I open the library manager, FirebaseDB deletes itself, even though I didn't tamper with it, I just looked at or checked which local libraries are already active. Maybe some people who don't understand Compile errors will be confused about fixing the error, even though it's just FirebaseDB deleting itself. Hopefully, you understand what I mean, my English is bad ;) and another thing in beta 7 it feels heavy when opening the application like it's lagging, if the previous beta 6.3 that you made feels light and responsive (without lag)

Please specify where the lag occurs and attach a picture.

[Ventili]

I still can't add this library to Sketchware Pro:
https://www.rustore.ru/help/sdk/pay/kotlin-java/10-3-0

The wrong provider is added automatically (I'm still testing). Bom support is needed, and it might already be implemented.
I compared the Manifest of the finished application with the integrated SDK, and it's very different from what this merger currently offers.
I also noticed that if the application is added via the Manager (a Java file without blocks), the imports aren't added (although I haven't tested it thoroughly yet).

[webmturn]

Thanks for the detailed report. I went through the three points and have a partial fix on the way; for the rest I need a bit more info.

1. Manifest differs a lot from a real integrated SDK — confirmed bug, fix incoming

LocalLibraryManifestMerger was only merging children of <application>, not attributes. So when a library manifest declared something like:

<application android:name="..." android:supportsRtl="true" ...>
    <activity android:name=".YourPayActivity"
              android:launchMode="singleTop"
              android:exported="true"
              android:windowSoftInputMode="adjustResize">
        ...

…and the generated manifest already had <application> and the same <activity>, the new attributes (launchMode, exported, etc.) were silently dropped. This directly matches what RuStore Pay needs (android:launchMode="singleTop" on the billing Activity, plus several <application> attributes).

I'm adding attribute-level merging with existing-wins semantics: your project / XML-command settings always win, library values fill in the gaps, conflicts are logged. It also merges attributes on the library <application> element itself.

2. BOM support (ru.rustore.sdk:bom) — not implemented yet

You're right, BOM (<packaging>pom</packaging>) is currently rejected by DependencyResolver (invalidPackaging). Implementing it properly means parsing <dependencyManagement> from the POM and using it as a version catalog for subsequent unversioned artifacts in the same session. That's a bigger change and the upstream org.cosmic.ide.dependency.resolver doesn't help here. I'll track it separately — for now, please add each ru.rustore.sdk:* artifact with an explicit version, and add the RuStore Maven repo (https://artifactory-external.vkpartner.ru/artifactory/maven-rustore-exposed/) via the Repositories UI.

3. Wrong provider added automatically — need a concrete sample

I couldn't reproduce just from reading the code. Could you share:

• the offending <provider .../> element you see in the generated AndroidManifest.xml (its android:name and android:authorities), and
• ideally a diff against the merged manifest from a real Android Studio build.

Likely candidates I considered: androidx.startup.InitializationProvider (only emitted when androidx.emoji2 / lifecycle-process / work-runtime is bundled), FileProvider authorities collisions, or a transitive AAR provider whose authorities don't get ${applicationId} substituted before being deduped. Without a sample I'm guessing.

4. "Imports aren't added when the library is added via the Manager (Java file without blocks)" — please clarify

There are several "Manager" entry points and they each behave differently:

• Local Library Manager (ManageLocalLibraryActivity) — imports an AAR/JAR. Doesn't touch Java sources at all.
• Library Manager (Firebase / AdMob / Compat / etc.) — toggles internal flags.
• Java file manager in the project file editor — creates plain .java files.

Which one are you using, and which import statements are missing where? A small repro project (or even just the steps + the generated Java file) would help a lot.

A commit with the merger fix will land shortly.

[xein666]

This is what I experienced after I added the FirebaseDB/auth component. In the event section (component section) I added a component to write code that always force closes or exits itself with an error notification, in more detail like this. After I successfully added the FirebaseDB Component in the event section, I wanted to add OnChildAdded, OnChildResume or others, but it always exits itself or force closes, so I can't add that component at any time. And maybe the same applies to other components. And finally, after we successfully added all the components (FirebaseDB, auth, etc.), if we open the Manager, the existing components will be automatically deleted, even though we didn't do anything in the manager, just opened the manager to check what was active.

[webmturn]

This is what I experienced after I added the FirebaseDB/auth component. In the event section (component section) I added a component to write code that always force closes or exits itself with an error notification, in more detail like this. After I successfully added the FirebaseDB Component in the event section, I wanted to add OnChildAdded, OnChildResume or others, but it always exits itself or force closes, so I can't add that component at any time. And maybe the same applies to other components. And finally, after we successfully added all the components (FirebaseDB, auth, etc.), if we open the Manager, the existing components will be automatically deleted, even though we didn't do anything in the manager, just opened the manager to check what was active.

It has been fixed, but it has not been rebuilt and released. You can build it yourself or I will send a fix later