Hi Erel,
Yes, I do realize that. The fact is that the libs run perfectly in B4A - no problem there. But when I try the obfuscation in the Proguard GUI I get an automated error regardind B4AShared (not Core). I just added that it appeared also something related to swing...but I think that if I can solve the problem with the shared b4a, I can solve the "swing" problem...whatever that is.
And of course I must maintain the main procedures available for b4a understands them.
Kind regards,
Kepler