Encountered typeIdOffset not 0? This is your report.

[iBotPeaches]

Hi there,

Apktool has intentionally output this error message because we need to find an application in the wild, like the application that sent you to this report.

Please attach the apk / email me (ibotpeaches (at) gmail (dot) c0m) so we can fix this issue.

[iBotPeaches]

This warning has been merged into master - #1690. Next release will have it.

[iBotPeaches]

Going to close this, I still get notification, but one less bug.

[Elmehdioub]

Going to close this, I still get notification, but one less bug.

You like to keep close issues with no fix, what a wonderful developer.

[Schoemiees666]

Did I do something wrong or is there something that I can go and fix assistentce will be appreciated Let me know

…

On Sat, 23 Dec 2023, 21:36 El Mehdi, ***@***.***> wrote: Going to close this, I still get notification, but one less bug. You like to keep close issues with no fix, what a wonderful developer. — Reply to this email directly, view it on GitHub <#1728 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/APH2FDEDHPI4SEDCFW3MOMLYK46DZAVCNFSM4ERBLQEKU5DIOJSWCZC7NNSXTN2JONZXKZKDN5WW2ZLOOQ5TCOBWHAZTKNZUGMZQ> . You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>

[REAndroid]

Hello,
I was researching same for purpose of "type id offset" I couldn't find enough resources thus I made my assumption as:
type-id = typeIdOffset + typeIdOnSpecHeader. Then I generated three apks(using my tool) with typeIdOffset = 0, 1, 2 and tested on two devices API-16 (4.3) & API-28 (9.0)

Here is my results:

typeIdOffset	API-16	API-28
0	OK	OK
1	OK	fail to load strings
2	OK	fail to load all resources

I am guessing that typeIdOffset is abandoned by android after some version.

type-id-offset-apks.zip

[iBotPeaches]

very interesting - thanks @REAndroid. Guessing the various newer iterations of packing resources became a more optimized approach than type offsetting which was probably part of the sparse era of optimization.

[REAndroid]

Yeah, i also run my test with assumption type-id = typeIdOnSpecHeader i.e. ignore whatever value on typeIdOffset for calculation of resource id 0xpptteeee , the result was aapt2(recent 33.0.1) parses correctly but both old and new api devices fails to load resources. I couldn't find any setter code for typeIdOffset on AOSP

I guess android has bug on recent versions, anyways we shouldn't care much cus no real apk with such resources

[bzdnagao]

“What does this project look like after it starts? I see this（> Configure project :
Building SNAPSHOT (no .git folder found)
fatal: No names found, cannot describe anything.
） when I run it in IDEA, does it have any impact?”

[iBotPeaches]

“What does this project look like after it starts? I see this（> Configure project : Building SNAPSHOT (no .git folder found) fatal: No names found, cannot describe anything. ） when I run it in IDEA, does it have any impact?”

This looks to have nothing to do with typeIdOffset - I don't understand? What is the relevance to this thread?

[REAndroid]

@iBotPeaches
Unrelated to this issue nor it is real issue to create new,

Do you have any idea how to handle styled string in xml attribute value ?
e.g:

<TextView android:text="<b>styled string</b>" />

I generated demo apk with styled string in xml string pool, and android device renders it correctly

Check res/layout/activity_main.xml
styled-string-in-xml-generated.zip

[iBotPeaches]

@REAndroid - Styled strings are the bane of my existence. The spec lies, apps lie, nothing makes sense.

• [BUG] Error parsing styled strings #3588
• [BUG] Chunk [end] is not a valid entry #2890

In terms of what you are looking for though for compilation - I don't know. I just have to build something to handle disassembly and let aapt2 do the heavy lifting again. Our StyledString class has all the details.