Thanks for the quick reply and your efforts to look into my questions.

1. function sc_ShowSearchAddress()
You are 100% correct, the code is correctly decompiled. I have figured out where the problem is: the defect is elsewhere but it caused sc_ShowSearchAddress to fail.
Sorry for not finding it earlier and comparing with later versions this module.

2. MODEL.lua.AddressSearchStreetsInState = MODEL.address.search.support_streetsearch_in_state(EAddressSearch.Result.selectedCountry)
I agree with you that it's not a decompilation issue. I concluded this too rapidly because I tested just one single change from the original deployed APK version (with same version): replace compiled address.lua with the decompiled one in data.zip. But in the meantime, I have seen 2 instances where the correctly disassembled file fails due to defects in the code itself. It seems that when compiled, the defect does not show or it shows elsewhere.

You are right that this function appears multiple times but it also "crashed" at every single invocation. I should have been more clear that this line does not generate a true application crash. It is as you say: the function is aborted, the "print" statement I added at the beginning of the function is shown, but not the one right after this particular line. The result however is that the app does not function correctly. I will add the extra tests you suggested. Maybe there is some corruption, since there is one other MODEL.address.search function that crashes as well (City search). The EAddressSearch.Result.selectedCountry parameter is verified to be correct.

3. The other question in post #5
The modified code works, so only if you have time to spare. Here I found the "problem" by comparing with an an older (nextgen) version that JiGoLUA 2.2.2 decompiled.
This was the only difference that seemed not related to code changes, and when changed to the nextgen version, resulted in correct execution, hence my suspicion...

I have now validated and modified over 20 (large and complex) files and have become very convinced that the disassembly you posted is very robust and don't expect to find any more potential disassembly issues. Unfortunately, correctly disassembled does not always imply "working as per the original".