Trying to build a applications with b4a 8.8 gives errors on multiple libraries. Refine this issue all seem to be related to UDG app-updating lib.
Using b4a 8.5 all works fine. Also App updating 1.3 and 2.00 without errors.
With 8.8 beta and app-updating 1.3 or 2.00 multiple errors come up, pointing to different libraries.
This seems to be a glitch in B4a 8.8. When 1 library is not accepted, multiple will be reported. See example
building the source code of Appupdating with 8.8 beta gives no improvement
Using the example AppupdatingEx200 found it compiled fine in 8.5, but gives following errors in 8.8
Note: as you see the phone lib is "missing", but in fact it's there. A glitch of b4a 8.8 i suppose.
a workaround for this glitch is to deselect the phone library, and activate it again. This will be alive for as long b4a is open and the phone lib is in memory. As soon you restart b4a again the phone lib will be reported again. But it's a glitch, started by the Appupdating lib.
So question is: is appupdating 1.3/2.00 not compatible with b4a 8.8 or some setting has to be done?
Using b4a 8.5 all works fine. Also App updating 1.3 and 2.00 without errors.
With 8.8 beta and app-updating 1.3 or 2.00 multiple errors come up, pointing to different libraries.
This seems to be a glitch in B4a 8.8. When 1 library is not accepted, multiple will be reported. See example
building the source code of Appupdating with 8.8 beta gives no improvement
Using the example AppupdatingEx200 found it compiled fine in 8.5, but gives following errors in 8.8
Note: as you see the phone lib is "missing", but in fact it's there. A glitch of b4a 8.8 i suppose.
a workaround for this glitch is to deselect the phone library, and activate it again. This will be alive for as long b4a is open and the phone lib is in memory. As soon you restart b4a again the phone lib will be reported again. But it's a glitch, started by the Appupdating lib.
So question is: is appupdating 1.3/2.00 not compatible with b4a 8.8 or some setting has to be done?