nufus42

Believe it or not, your idea worked. I've extended the options of all the PendingIntents in System.Android.Notification (after copying to my project folder) with "or TJPendingIntent.JavaClass.FLAG_IMMUTABLE" and my error is gone and my weekend is saved (at least the sunday). Thanks man! I've read a lot of your comments, when I silently tried to find solutions for my problems and most of the time they at least helped me to find the right way. If our ways should ever cross (quite umlikely because we're living in totally different parts of the world - Germany here) I would be honored to be able to buy you a drink or two.

Hi @all, I mostly surf the net if I'm stuck, but this seems to be a first timer for Delphi developers. No cerresponding answer pops up. I developed an app with 11.1 for Android target 30 including push notifications and local notifications. Works great. But... Play store says: you're not on level 31? You're not coming in! Alright; I do the manifest trick to fake SDK level 31. Play store accepts. I am happy. Until I try the first push notification with an app downloaded from Play Store: java.lang.IllegalArgumentException: <appname> Targeting S+ (version 31 and above) requires that one of FLAG_IMMUTABLE or FLAG_MUTABLE be specified when creating a PendingIntent. Dear god, ever heard of defaults, Google? So I installed SDK 31 since I assumed the problem would be solved by that. No, it's not. Is it the NDK? I did not update that, since I did not find a matching NDK (platform folder is missing or prebuilt etc.) I wish Embarcadero would maintain that better besides urgeing you to an update of Delphi. Would updating Delphi to 11.2 or 11.3 really help? That's time I would like to spare since I already crashed the deadline of this project due to the notification problem.

Just to wrap this up: As @mvanrijnen (Thanks!) suggested in the end it was a missing dll or at least two of them. The debug file actually helped. If you know how, it is quite simple: In the section [Server.Logging] you uncomment the row that begins with Filename. And set the path you desire. You can actually write manually to that log with TEMSEndPointEnvironment.Instance.LogMessage('test'); Unit EMS.ResourceAPI is needed in the uses clause.

Thanks for your answer, but I'm afraid it won't help. I haven't been precise enough in my first post. The package isn't even "loaded" in IIS when I include TRESTClient or TNetHTTPClient (and corresponding units).

Not the exact answer to your question, but I assume it could help you out if you redirected the call through a rest proxy service like www.intercept.rest.

I've got a wierd problem with a RAD Server package. It's working fine with emsdevserver or RS Lite but not in IIS. The problem seems to be either TRESTClient or TNetHTTPClient. If I put any of those into the package it is still working fine under dev but not as IIS module. It might be a configuration problem with the IIS, but I'm a programmer not a web admin. Which leaves me without a clou. Did anyone experience a similar behavior and could solve it?