( Mods - Please move this topic to the appropriate location if it is not here now. Thanks. )
Seems as though things have gone Crazy over at Google. The Latest .api 29 Target Version 9, has been causing a ton of Issues. Both with MMF2.5 DEV and Older extensions like the ANDROID SMS Extension.
Which Honestly, this should be Removed from the Click store, do to not being able to use it anymore and the Author: Przemysław Prygiel, has yet to update it.
ANDROID SMS: https://clickstore.clickteam.com/plugins/extensions/android-sms
Basically, I was hoping as a Group. We could figure this new Nightmare out, by creating and testing our own Extensions here.
As far as something that Kind of works now. The ANDROID OBJECT can Send the Information to be added to a Text Message, but requires the Default Messenger Application your phone comes with to send it.
Information on how to do just that: https://community.clickteam.com/threads/106189-Show-the-way-to-send-a-SMS-with-MMF2-5
However, the post above is not what a APP Developer would actually want for their own app. Simply because, if you are creating your own SMS application. You would still need to use another Default Application within the users Device, to send your Message.
Prior to Android 29 at Target 9. You could use ANDROID SMS Extension and it worked Fantastic. However, with all the new Changes from Google, most extensions for MMF2.5 Dev are becoming a thing of the Past.
If anyone would like to tackle this Project. Let's do so below.
Here is some info that I found, that may help out a ton with this project. Basically, it explains why I believe the ANDROID SMS object is no longer working and crashes an app compiled with the Latest api / Target Version, using it.
LINK to Info: https://proandroiddev.com/no-more-sm...t-9b8226de7827
Which coincides mostly with Current Android Object procedure: https://community.clickteam.com/threads/106189-Show-the-way-to-send-a-SMS-with-MMF2-5
Thanks for any Help in advance...