Dalija Prasnikar

That value 26.1.1 seems to be hard coded somewhere and is basically meaningless. What you need to do is go to SDK Manager, and under SDK choose appropriate platform folder: SDK API level location C:\.....\sdk\platforms\android-28

Well, then Android doc got it wrong 😉 https://developer.android.com/guide/topics/manifest/activity-element.html#resizeableActivity

android:resizeableActivity was added in API 24 if your target API or SDK platform is lower than that version that resource identifier will not be recognized.

If they add warning they could just as well fix it... Seriously, no matter how hard I try, I cannot figure out the real reason why...

Memory-Leak on Const-Parameter https://quality.embarcadero.com/browse/RSP-10100 Also specifically for ARC compiler, above problem can also cause crashes (linked with above report) Leaks or crashes on passing freshly created object instances directly as interface parameters https://quality.embarcadero.com/browse/RSP-17071

This is rather sad fact(s). Both that talking about bad coding practices is considered trolling as well as fact that after of decades of discussions and knowing that certain code is bad it is still widely used and all warnings are ignored. Embarcadero cannot possibly take in account every single line of code out there. Problem here is inherently in 'with' and not in adding additional functionality. Every change has potential to break some code somewhere, but with attitude that nothing should be changed we would have no progress. That does not mean that bad code changes will not happen. We are not discussing other languages here. 'with' is the problem within language itself. You can shoot yourself in the foot with 'with' even in single line of code. Again, main problem is that code may break due to far away changes you may not even be aware of. 'with' makes code fragile and prone to breakage more than it would be without it. Any code can be broken one way or another. Point is minimizing accidental and subtle breakage as much as possible. On this we agree. With every rule there are few exceptions. That does not mean we should not strive to educate about particular code dangers, especially when benefits are minimal or non existent and can be obtained by using different techniques.

We are talking about TRect here. Very basic type used all over. It is not very likely that one will create his own types for just about everything. And this is where using with can easily break your code without you even realizing it is broken. This is especially problematic when used in combination with UI where testing is hard and you can have a lot of code that is poorly covered with tests that could reveal such issues. 'with' is relic of another time and another coding practices. And, yes you could shoot yourself in the foot even back then, but now it is extremely easy to do so. Not using 'with' is the best advice one could offer. It is almost like using goto and absolute. You may have some very limited use case where using it is justified, but you will not find such constructs being used at large.

There is open report requesting App Bundles support. Anyone interested in Android please vote for it. https://quality.embarcadero.com/browse/RSP-25625

While IDE automatically "adds" project to "new" group when you open project, it never forced me to save that group. Maybe you are changing something "group" related so it requires saving.

This is long standing issue... I even had bug report in old QC related to this. Problem is not only that it compiles multiple projects when you only want one, but it messes up compile defines and you can end up with total mess in the resulting exe. I eventually gave up, and I no longer have multiple projects in a group. You can try filling bug report in QP and hope it will be solved one fine day.

In addition to what @Stefan Glienke said, on Delphi LLVM based compilers exception triggered by accessing nil reference will wreak havoc because it will not be caught by current method exception handlers (and finally blocks will not be executed either)

Warnings are just a warnings for a future. It is wise to read those, but they don't prevent publishing.

Working as designed. Compiler evaluates mathematical operation first and only then it will do assignment. Since your operation works on two integers, the result will also be integer - and it will overflow at compile time. You need to typecast at least one of the operators to Int64 to widen operation result.

I never realized that some libraries were available only through GetIt. This is a problem indeed. I guess that best course of action would be submitting QP report (once it finally gets online) and post the link here so we can vote on it.

Like others have said, GetIt is good for newbies, hobbyists, it is not really well suited for professionals - only if you want to try something without too much hustle... But using GetIt for downloading Android SDK/NDK is pure masochism. Uninstalling/Installing that every time you need to update Delphi.... WHY???? You have several options... download with GetIt, then move (copy) that in some permanent location... or IMO the best option, go to https://developer.android.com/studio and download Android Studio it will also give you tools for additional monitoring and inspection of your Delphi app. Or if you really don't want whole Studio... you can also download SDK separately. You can share same SDK across different tools and Delphi versions. No need to keep separate versions or update it every time you update Delphi.

Most likely path to Command Line Tools on your Mac is not properly set. How to check and setup you can find at Troubleshooting (macOS and iOS) section http://docwiki.embarcadero.com/RADStudio/Rio/en/SDK_Manager Or if you have Xcode installed you can go to Preferences and set Location (path) to Command Line Tools http://docwiki.embarcadero.com/RADStudio/Rio/en/Installing_the_Xcode_Command_Line_Tools_on_a_Mac

... as well as previous owners.

No, it is not fixed, yet. Permanent solution that will solve all those issues is Delphi LSP (Language Server Protocol) support and is scheduled for 10.4.

Works fine here.

@Darian Miller What you are talking about and what I am talking about are two completely separate issues. This thread revolves around brand new 10.3.2 release... in order to install that release you need to be on active subscription for which you can get license bump... and my comment was strictly about the fact that even though you can, you might want to avoid such situation because you will find yourself in situation where you have to wait and while you wait you cannot work...

License is perpetual, but at some point people would not get license bump (for any version) if they were not on active subscription. That situation was kind of resolved in the meantime... but it is still not quite clear to me what is current status and how it works... if I recall correctly now you have to contact sales to get registration bump

You would not be able to install/use 10.3.2 (or any new version that will be released) without being on active subscription anyway. So having a bump approved is not an issue, it is the waiting for the bump that matters.

Indeed. I just always like to read MS documentation first. So those would be my first steps. After I collect all necessary API calls, I would search Delphi RTL/VCL source to see if anything is already implemented somewhere... and yes, then Google again for specific Delphi implementation if needed (I can generally manage using Windows API calls without additional searching, but that knowledge depends on how often one has to interact with Windows API directly - Delphi does good job at hiding and wrapping those parts so many developers don't have the need to do low level interactions)

Knowing what needs to be done is quite different than having that particular piece of code at hand for sharing.

1. Google create process 2 Google process pid 3. Google close process 4. Google wait for process David gave all necessary steps... you (or anyone) just need to go through that list one by one finding out how to do each particular thing if you already don't know how to do that.