iOS Build Environment Help Center

Crash on first time app start (+2 questions)

Roman

Windows 11
Builder 3.56
SDK 16.2

Hi,

You might be remember me from the last month "discussion" here. First of all would like to apologize for being rude. I hope you may understand I was really upset of the fact how much time I spent trying to setup the builder without getting the result.
However, I finished that task even before your next release (where you fixed that duplicate symbols issue) and created the build. Yes, super complicated for the first time, but at least your builder worked in my case.

I hope you may help me with few other issues I met.

1. App crashes just after I install new version by OTA. This doesn't happen in 100% of cases, I would say 50%. After app crashed I can use it again without any problem. Tried to google by an error from the builder console log, but didn't find much.
Here is the crash log - https://pastebin.com/hXHrvfm2
And here is the log from the next launch - https://pastebin.com/36xQ3mk4
Same happens if I upload the .ipa to TestFlight. Note, that direct XCode build works fine

2. By some reason I can't build if I set on Build Settings `script debugging` and `wait for managed debugger`. I can't provide the log currently, can do next time if only the builder, in general, canwork with these settings? Can it?

3. I still can't understand the idea of build cache. I didn't find much info hereon the forum, so would like to clarify - how does it suppose to work? The problem is that each time I am trying to use cache after previously succesfully build package, I get the errors.
Are there some specific cases when it can be used? For example if I change scripts in the project only? Or scenes? Or prefabs? Please clarify it. If something I will provide the log if needed

:: @Roman added on 03 Jun ’23 · 17:36

That's the log for #3 - https://pastebin.com/aezg33e5
I changed scene and some scripts

:: @Roman added on 03 Jun ’23 · 19:19

#3 - updated to 3.57 and tried to build same project using cache.
It was completed successfuly but with a tons of errors in log - https://www.dropbox.com/s/vq7evlfap0hxt1g/build.log?dl=0

RSS

Replies

#1. Pierre-Marie Baty

This message will be left intentionally unanswered.

You can't post a 1-star rantastic review with words such as "DON'T BUY", "Complete trash asset" (your words), *leave that review online* after discovering that the next update of the asset fixes your problem as promised, and come back with a heart-shaped mouth expecting me to provide you with support after such a behavior.

Please improve your review, it has potential to be even more deterrent now - and see if I care.

In the meantime, this thread will go sticky so as to show users how NOT to behave here.

Moderators: Pierre-Marie Baty