SetupInAppPurchase 'External exception 1' in Android 64-bit

[Juande]

Hello.
First all sorry for post in English.
I have been using the Bigjorj solution for InAppPurchases in my app in Android 32-bit since I found in this forum with success;

Recently I tested code in Rio 10.3.3. Android 64-bit for Google requirements and get an error 'External exception 1' , my code is as follow in OnCreate form event in first lines;

             FInAppPurchase := TInAppPurchase.Create(Self);
             FInAppPurchase.ApplicationLicenseKey := '****';
             FInAppPurchase.ApplicationLicenseKey := FInAppPurchase.ApplicationLicenseKey +  '****';
             FInAppPurchase.ProductIDs.Add(PremiumVersion);
             FInAppPurchase.OnSetupComplete := InAppPurchaseSetupComplete;
             FInAppPurchase.OnProductsRequestResponse := InAppPurchaseProductsRequestResponse;
             FInAppPurchase.OnPurchaseCompleted := InAppPurchasePurchaseCompleted;
             FInAppPurchase.SetupInAppPurchase;

In last line 'FInAppPurchase.SetupInAppPurchase;' is when exception is throwed 'Extrernal exception 1.', I accept the error that continues displaying several times until  the app crashes and exit suddenly.
Code of SetupInAppPurchase procedure within FMX.InAppPurchase unit is;

procedure TCustomInAppPurchase.SetupInAppPurchase;
begin
  if FInAppPurchaseService <> nil then
    FInAppPurchaseService.SetupInAppPurchase(Self)
end;

I have tested removing this last code line and error doesn't display, but users that purchased the product get the version lite and users that want to purchase it get message 'In-App Purchase component is not set up', logical, the result expected because InAppPurchase never has been set up.

Anybody with similar issue and got a solution?

Many thanks and regards from Spain.

Juande. 

[Joe]

Hi,

i have the same problem, i cannot use inapppurchase when compile in ANDROID 64 bit !!!!!
I've try to place some debug message in FMX.InAppPurchase.Android and FMX.InAppPurchase but 
also there nothing raise exception, i hope in a quick solution , this is clearly a bug of RIO 10.3.3 
 

[Brovin Yaroslav]