Dave Nottage

Mine works OK with that unit in it.

OK, for some reason I was under the impression that it was being raised when the socket was closed without an attempted read/write. I'll have to revisit that, thanks 🙂

It's the most annoying exception, ever. It's a permanent "ignore" in my exception tracking code. It'd be great if it was just removed, permanently.

Compiles OK here.

I'm able to use FireDAC with SQLite OK in the demo you refer to. Can you provide a test project for the TDSRestConnection issue?

There's an image here with EXIF data: http://orchids.enwphotos.com/2013-1/310.html Which includes the camera make etc. I use a Chrome plugin to view the data: https://chrome.google.com/webstore/detail/exif-viewer/mmbhfeiddhndihdjeganjggkmjapkffm I doubt it, since the camera make and model is in text form, not an index to different models Are you referring to Delphi code? Also, description and title are not known tags - perhaps you're referring to ImageDescription? There's a list here: https://www.exiv2.org/tags.html. Note that not all images will have anything in this tag. There's an answer on SO that suggests a simpler method of extracting EXIF at least in relation to JPEGs: https://stackoverflow.com/a/18624442/3164070 There's also a couple of alternatives to CCR-EXIF, here: https://torry.net/pages.php?id=104

I suspect that attaching an image file here strips the metadata, since the one you attached appears to have none, or at least the EXIF data is gone.

Whoops! Yeah, I actually discovered that after my comment on the report. I've now updated it. Please refer to my comments on the report: https://quality.embarcadero.com/browse/RSP-18329

Incidentally, I suspect that leaving it "acquired" can consume a lot of battery (due to what happened to my device), so it might pay to check when the screen locks and do a release.

As far as the MulticastLock goes, you should call acquire when your app needs to listen (i.e. when your TIdUPDServer is active), and release when it does not. That said, I've given up on Indy for multicast because there have been too many hoops to jump through, including for Android.

There does not appear to be anything in the log that gives any clues as to why it hangs. This why it's important to also use the debugger and/or refine the code into a reproducible test case.

As far as the SDK settings go, I believe it derives the JDKPath from one or either of the JDK settings: You can check this in the registry:

Nothing so unusual: it takes less than a second.

Mine is currently 1920x1074, but changing it does not make any difference for me; the behaviour is still the same.

The Output tab of the Messages window usually has the details of the compile error.

Reported this a couple of months ago: https://quality.embarcadero.com/browse/RSP-26998

Have you tried tracing the code via the debugger? Can you provide a reproducible example?

Yes, I have that issue too. I've been meaning to report the problem. It presents the prompt every time you run it? Which app is this?

Thanks for the tip! I wasn't aware of tags here, and they're a bit small but at least now I know to look 🙂

Not that it would affect many users (if any), but in FMX.Edit.Style: protected FNeedChange: Boolean; procedure Change; virtual; { Messages From Model} procedure MMSelLenghtChanged(var AMessage: TDispatchMessageWithValue<Integer>); message MM_EDIT_SELLENGTH_CHANGED; procedure MMSelStartChanged(var AMessage: TDispatchMessageWithValue<Integer>); message MM_EDIT_SELSTART_CHANGED; procedure MMCheckSpellingChanged(var AMessage: TDispatchMessageWithValue<Boolean>); message MM_EDIT_CHECKSPELLING_CHANGED; Spot the typo. The last method name pictured is ironic. Someone should whip up a "spell checker" (of sorts) to see how many of these there are 😉

If by "setup" you're referring to how to set up a project in Firebase Console, you should start here: ..and watch until the 4:52 mark (the rest is not relevant to Delphi) For Delphi code to implement FCM on iOS, you could refer to this article: https://www.delphiworlds.com/2020/01/expanding-embarcaderos-fcm-implementation-revisited/

It would help to specify which platform(s) you want to achieve this on. If it's iOS/Android, then using the OnCallStateChanged method of IFMXPhoneDialerService is supposed to allow you to know when an incoming call starts, and using the GetCurrentCalls method should contain the number. That said, iOS now restricts being able to access the actual number. Also, I know others have had problems with making IFMXPhoneDialerService work at all on Android. I don't know whether that's the case now, however I use my own (non-public) code for it anyway.

This person seems to have it working in 64-bit: https://forums.embarcadero.com/message.jspa?messageID=671467&tstart=0

Remove the [Weak] attribute from FIAPService. Might still be a bug, though.

Apparently this is the reason: https://developer.android.com/about/versions/marshmallow/android-6.0-changes.html#behavior-hardware-id I nearly fell off my chair when I read that: essentially give up your location privacy so no-one can steal your Bluetooth Mac address? Perhaps someone else can explain why that's a good thing.