1. The terms are important. There is no such thing as SDK 28.
2. There is no relation between the 64 bit requirement (which almost all apps meet) and setting targetSdkVersion to 28.
The issues or limitations are not related to B4A. There are new requirements that you should meet. As I wrote they are quite simple to meet and everything will be explained. You will have more than enough time to meet these requirements.
Hello
@Erel . I understand that the limitations and changes are related to the Google decision which is implementing all the new security restrictions and upgrade requirements in the new Android version (V9 - Pie). The 64 bit requirement has a "side" relation with sdk 28... see:
1. Starting at November-2019, all apps must to be 64 bits compliant
2. Also the new apps will need to use SDK 28... no SDK downgrade will be allowed
Some of .so native libs recompiled to support 64 bits could eventually don't work with SDK 28... and that's why we are testing together SDK 28 AND 64 bits libs... about the time requirement, due its complexity I estimated that for some libs (SIP lib based on pjsip for example), we could spend 60-90 days to get a new stable version and more 30 days in beta testing with users... that's why we are worried about time.