Setting android reference absolute path in projectfile produces errors

Elements EBuild
1

Using the Android SDK template, the elements file contains (omitting “Cooper”)

  <ItemGroup>
    <Reference Include="android" />
  </ItemGroup>

Now EBild says:

Reference ‘android’ was resolved to ‘d:\Flucke\AndroidNew\platforms\android-34\android.jar’ for target ‘Cooper-Android’.

If i now replace the “android” reference with the resolved location like so:

  <ItemGroup>
    <Reference Include="d:\Flucke\AndroidNew\platforms\android-34\android.jar" />
  </ItemGroup>

EBuild says:

Reference ‘d:\Flucke\AndroidNew\platforms\android-34\android’ was resolved to ‘d:\Flucke\AndroidNew\platforms\android-34\android.jar’ via absolute path for target ‘Cooper-Android’.

Should be the same, right ? But the project doesn’t compile anymore :frowning:

org.me.androidapplication 1.bugreport.txt (13.0 KB)

2

Sorry, the web app removed the intresting projectfile parts.

First Part (replaced the greater then signs etc…)

ItemGroup
Reference Include=“android” /
/ItemGroup

Second Part:
ItemGroup
Reference Include=“d:\Flucke\AndroidNew\platforms\android-34\android.jar” /
/ItemGroup

3

You have aapt2 errors processing reousrce files. These will be unrelated to that android.jar file you reference. THAT said, why do you hardcode the reference to the android.jar file, and are yu sure its the right one?

4

I do so with all my references… and yes, im shure it’s the right one.
Using Water exclusively, this wouldn’t matter, but using EBuild alone (or in my case in my App) this matters…

5

Okay, but why? I think that’s a very bad idea, and you shouldn’t do (nor need to do) it.

Ok, so just to be clear, aapt2 fails when the an absolute hint path is provided to android.jar`, but does nit fail, when the exact same android.jar gets found automatically?

TBH, that makes sense and should make no difference.

IN any case, I suggest leaving the hint path off android.jar, as that’s bow it’s supposed to be. Especially if adding it does break things for you.

Can you elaborate what yo mean Water vs EBuild alone? the build should be exactly th same, whether you trigger hot inside Water or form the command line. Can yo compare the arguments Water passes to EBuild vs what you use manually, to see what could be. taking a difference, if any?

thanks,
marc

6

Hi Marc,
i only ment that Water uses/cares of taking the android.jar file without path.
I’ve changed this on my side, so this is kind of ‘would be nice’ now.

7

Btw: i cannot get an Android App to install/run either on the emulator nor on the
device. What do i miss ?
The crossbox dropdown shows me the (virtual) devices, but ‘run’ remains grayed out.
The latest SDK doesn’t produce apks any more, and when setting this to true in the project options it gives an error.
Manually using the bundetool produces apks without (debug-) certificate, so
i cannot install/run them manually.

Should i open a new thread or what im doing wrong here ?
(Cmdline tools version 13, build tools version 35)

8

That is the issue, pas per the other thread.

It used to be, .aab was the new format to build for deployment, but debugging still required .apks. That’s the last state we support currently. At some point after, Google apparently removed the ability to create .apks, so I assume that debugging with .aabs is supported now by the SDK (but not by us, yet). in the preview thread where we discussed that, I logged a ticket, and one of my colleagues is looking into supporting this scenario in a future update, hopefully soon.

yours,
marc

9

Sounds good, thanky you :slight_smile:

10

Hi,

i found this in the latest changelog:

“Android: support for building .apks files (wip).”

but cannot find any changes in the bahavior.
Can you please give some further information how to achieve this ?

Thanks

11

This is not fully working in last weeks build, but should for the upcoming 2957, on Friday.

Essentially, theres a new project setting, GenerateAPKs (note the S!); if on, the build will generate a .apks file from the .aab, and use that to deploy to the device or emulator for debugging. You can turn off the GenerateApk setting (I’ll probably remove it in the future, as latest SDKs cant do this anymore, ayways; and it now defaults to off).

I’m still undecided on whether I’ll have GenerateAPKs ON by default for Friday, or whether to just set it to ON for the Debu config, in the templates; in the after case, you manually have to turn it on for existing projects.

(w/o the option set, deployment will continue to fail with

~> Debugging with .aab files is not supported yet. Please enable building an .apk(s) file.

12

Thanks

13

Cannot get it to work (.2959). What do i miss ?

14

You tell me. What fails?

15

Can you supply/link to a working example ?

16

For what, exactly?

A new Android app from template builds, deploys and runs fine, here for me.