Uploaded build error: App thinning

[trevix]

Hello.
I have a published iOS and Android app named Referi, developed using OSX 26.5, LC 10.0.5(RC1).

Recently I uploaded with Transporter an update to App Store Connect, for internal tester, but the build and the following upload builds attempts to Store Connect, were always marked with the status "processing in progress" and cannot be downloaded to test users.

After numerous attempts and Apple support requests, I was able to talk on the phone with Apple support.
The operator told me that my build has a problem with App thinning and she sent me a link to this page: https://help.apple.com/xcode/mac/9.0/#/devbbdc5ce4f

My problem is that I don't understand what am I supposed to do with these informations. I hope someone can help me out with this.

Please note: these are the additions that I made to the updated build vs the published one:
- NFC reading of text from inside the app
- BLE (Bluetooth Low Energy) iBeacon listening (from custom BLE devices)
- The Android version of the same update does not have any problem and works well

Thanks for any help.
Trevix

[trevix]

This forum is increasingly looking like a self-analysis tool...

I found some armv7 code inside my extensions and thinking that this could be the problem, I removed it and reloaded the build to Test Flight.
Same result: the Transporter upload goes well but the status of the build does not make it available.

Still looking for an answer.
I wonder about the..."bitcode" factor. I don't even know what it is, but could this be of concern?

[stam]

This type of thing can usually be solved or mitigated using AI - I personally recommend Claude, but any AI will probably do.

Just literally copy the text of your question there and provide:
1. LiveCode version.
2. Xcode version.
3. Exact App Store Connect rejection text.
4. Whether any third-party iOS libraries/externals are included.
5. The Transporter upload log (or App Store Connect processing email).

If it’s fixable this will fix it. If it’s not fixable and you’re on the latest LC version you should contact livecode’s support. If you’re on an old LC version you may be less successful

[trevix]

After almost a month (!) from my help request to Apple and after several calls and messages sent to them, they told me what was wrong with my build.
Inside the package there were 2 "empty" pList, beside the correct one.
Don't know how they got there.
I would assume that somehow the LC Standalone setting gets confused ( it needs a serious update, anyway).

I worked a lot with Claude, in order to find the problem, that now is solved, to no avail.
I should have done just a single request: "look inside the package and tell me if there is something wrong." Oh well....

Trevix

[stam]

Glad you got it sorted...

Unusual that Claude didn't find the issue... Did you user Claude Code in Desktop? I find the desktop simpler to use that in terminal.

It will inspect your local files directly and should have picked up this issue. Claude as a chat bot is fine, but Claude Code is orders of magnitude better - not only can it inspect local files with minimal prompt and write to these where appropriate, but it writes memory files to the hard drive so it doesn't forget past events, incredibly helpful.

Of course if you did use Claude Code locally then that wasn't the answer...

[trevix]

Since I discovered Claude Code, through a friend, I was really into results and didn't have time to explore Claude Code very much.
I use it on a OSX terminal, where I paste, when needed, the directories for it to explore (in this particular problem, I didn't think of pasting the iOS package of the app...sigh).
I stopped using the Claude.app since Claude code tends to be a little verbose and more manageable in the terminal.
The nice thing is that it enabled me to create LCB extensions, with Claude code compiling for me Java and C code (with I both don't know at all).
When I need to solve complex problems or go back to previous problems, I ask Claue to save a CLAUDE.MD file, which, in most case, is enough to restart a conversation.

Overall, it is pretty amazing and over the last months Claude became better and better both on LCS and LCB (In the beginning I had always to remind it to re-read the LC and LCB dictionaries).

My only real complain is that Claude code cannot read the LC binaries of stacks, substacks, cards, etc and my app is too articulated to use script only stacks.
I hope that Create Classic 12 will solve this problem so that I will be able to ask:

"Please, read my stacks (or whatever) and look for problems, bugs, and better way to do things. Report the finding with your LCS solutions".

It would be great...

I am interested in knowing how other LC users use Claude Code, so that may be we can all get better with it.
May be it would be useful to have in this forum specific "AI" topics.
But I am not sure anymore of how many people are still active in this Forum, beside me, you and a few others
Trevix

[Emily-Elizabeth]

I use Claude Co-work (Sonnet 4.6) to work on HyperXTalk (engine code, IDE scripts and extensions). I use the desktop application. It seems pretty knowledgeable about what it is doing. I am really surprised at how well it handles the scripts, as I figured such a niche language would be challenging to Claude. Some times you have to correct the script (just tell Claude what's wrong and he remembers)

[trevix]

@Emily
I think you are taking advantage of all the things that, against my will, I had to explain over and over to Claude code

[Emily-Elizabeth]

I think you are taking advantage of all the things that, against my will, I had to explain over and over to Claude code

hahaha... Thanks for all the help