You need something that uses proper Gradle references, as my fix needs rthiose to determine dependencies between packages. You cant just reference the .aars.
What that is, is up to you. but it probably cant include appcompat, for the above reasons (because your fix depended on locally patching that package, which is not feasible). Consider appcompat a broken package that cannot be made to work.
Use the next build after the 20230303-191417-elements-develop one that is running now. The 191417 ones does not have my fixes yet.
These references are the same as In Android Studio - i will try with gradle ā¦gradle for appcompat were broken earlierā¦ Of course i Will try with gradle references the same I have in AS - no problem.
I can do thisā¦
The dependencies are in their metadata of the gradle, yes, alongside the aar (or jar). Form just the aar, thereās now way to see dependencies lies (afaik, though I could dig into that, at a later time, so see kit I missed a bit of info)
Error is the same āalphaā - references in gradle are the same as in Android Studio.
People form Xamarin fight too but they have success , but the worst thing is that this is library taken from their repositories which of course worked with aapt and has many errors in newer version too.It is recomended by google but how to use itā¦ I think that Google repair these errors in environment. I have no idea what to do , but the worst think is that I have to rewrite 3 apps ā¦using of course some code from libraries I did ā¦
I hate them ā¦
This Android environment has many errors and these errors are repaired inside itā¦and they are problematic for other tools suppliersā¦
Itās a pity, maybe Google doesnāt want competition in this matterā¦ I donāt knowā¦
So , the only way is to use AS so as not to hit the head in the wall in the futureā¦
Wrrrrrrrā¦
anyway, thanks for trying @mh
Have you tried with this --merge-only Only merges the resources without verifying resource references. This flag should only be used with the --static-lib flag.
So have two tried the new build? Because all three off these responses were posted before that build was even read and I cant really make heads or tails of them
The āalphaā issue is NOT what I fixed. the āalphaā issue is a valid, proper error because appcompat uses values that arenāt there. appcompat is broken (for latest Android SDK/Androis tool chain), and there is nothing I can do about it, because its the package itself that is broken. It uses something that isnāt there, an no fix of mine can fix that, as far as I can tell.
The fix I made was that valid packages that depend on other packages, and depend own resources from those other packages, should now aapt2 link correctly. Assuming they are valid, and dont use stuff that isnāt there.
Yes it does. I know that problem is not yours right now only my because for appcompat there are many problems and errors anx these errors are repaired by plugins and android studio. If these appcopat doesnāt work my 3 apps not working too and i have think whats next.
