The backside of this is that the compiled version should be considered beta 1 and not even close to the release. This is so due to the fundamental breaking change that the compiler makers have made by changing the size of Longint type.

So if you plan to use this version in production, please release it as a beta version to allow for at least some testing by the users.

We will do the tests of 64-bit iOS version in the next 2-3 weeks.

Let me note that FreePascal version for iOS (actually the same SecureBlackbox ccode), where there were no such breaking changes, has been working fine on 64-bit iOS since February. So it's only Embarcadero to blame for possible issues.

32-bit iOS version and Android version should work properly and can be safely used in production -- there were no dramatic changes in SecureBlackbox 13 that would cause any problems (there were a couple of breaking changes in API declarations, but nothing serious).

Hi Eugene,
great news. Thanks a lot.
I'd rather blame nobody - it is great that you support the datatype change in your codebase and it is good that Embarcadero is not preventing breaking changes in their product if they are needed for what they are heading for.
I understand that I should not use this version of SB13 in production settings - thanks again.

Another poblem might be for you the more-work you have because of maintaining the NG codebases for older versions.
IMO if you do mobile with Delphi you will develop with the last two to three most current versions, so you might consider to stop maintenance for the versions prior to XE8 - but I also could imagine that this might harm quite a few people in your customer base.
I hope that the mobile development environment will become more stable in the future.

We have customers who still use Delphi 5 (they have to license SecureBlackbox 11, because SBB 12 code can't be compiled due to Delphi 5 compiler bug).

Also it's not a problem of older mobile vs newer mobile version. It's a problem of say XE7/Win64 vs XE8/iOS64, where Longint and Longword types have different length. Even when you develop with the latest version, you still have your code broken (until you rework it, of course).