Re: Consumable In App Purchases on Android

2023-08-09 Thread Dan Friedman via use-livecode
Panos, Again, thank you for your help! mobileStoreProductProperty works beautifully! As for the lesson, it’s not that it could have been better, it’s actually pretty good (as most LC lessons are). It’s just that it needs to be updated to reflect newer methods and procedures. Given how lon

Re: Consumable In App Purchases on Android

2023-08-09 Thread panagiotis m via use-livecode
Hello Dan, Thanks for the update. RE 1, I *think* yes, but I would suggest you double check this anyway. RE 2, I would suggest not using mobilePurchaseGet(). This function is from the older API for in-app purchases, and we have kept it for backwards compatibility. I suggest using mobileStoreProd

Re: Consumable In App Purchases on Android

2023-08-09 Thread Dan Friedman via use-livecode
Panos and others… First, thank you for your assistance and advise with this. Panos’ suggestions were spot on!Restoring the purchases, then calling mobileStoreConsumePurchase worked for consumption. And, adding a “complete” case to purchaseStateUpdate and handeling the mobilePurchaseGet(

Re: Variable Watcher disappeared

2023-08-09 Thread Geoff Canyon via use-livecode
You can also accomplish most of this by right-clicking a stack in Navigator, and selecting Go > Show on the popup menu. That centers the stack on screen and shows it. It's meant to be guaranteed, so if there are other steps to take to ensure a stack presents itself, I'm happy to add them. On Tue,

Re: Consumable In App Purchases on Android

2023-08-09 Thread panagiotis m via use-livecode
Hello all, Also, it might be worth trying this as well - add a new button with this code: on mouseUp mobileStoreEnablePurchaseUpdates mobileStoreRestorePurchases end mouseUp Then press the button, and *then* call mobileStoreConsumePurchase pProductID . Hopefully now it should be properly c

Re: Unable to build for Mac: adding ad-hoc signature failed

2023-08-09 Thread Mark Smith via use-livecode
Very useful info Matthias. Thanks for posting. Mark > On 9 Aug 2023, at 2:41 pm, matthias rebbe via use-livecode > wrote: > > Every version of Xocde come with it own version of command line tools. > If you are just creating macOS standalones then you just need the command > line tools. > But

Re: Unable to build for Mac: adding ad-hoc signature failed

2023-08-09 Thread matthias rebbe via use-livecode
And like the links says that Mark posted. For iOS standalones every Livecode version supports a special Xcode version according to the installed macOS. You'll find the information which works for your installed LC version also in the release notes of your LC version. You'll find the release note

Re: Unable to build for Mac: adding ad-hoc signature failed

2023-08-09 Thread matthias rebbe via use-livecode
Every version of Xocde come with it own version of command line tools. If you are just creating macOS standalones then you just need the command line tools. But if you are also planning to create iOS apps then you'll need the complete Xcode package. To install just the command line tools run th

Re: Unable to build for Mac: adding ad-hoc signature failed

2023-08-09 Thread Mark Smith via use-livecode
Hi Dar, > Does installing Xcode change the command-line tools? I think it should. Others will correct me if I’m wrong. > I’m willing to install Xcode, but before that maybe I can provide some > information (such as version) about any particular tools. I don’t know if this is of any help but

Re: Unable to build for Mac: adding ad-hoc signature failed

2023-08-09 Thread Dar Scott via use-livecode
I wonder. I don’t have Xcode installed on this machine. Does installing Xcode change the command-line tools? Maybe those tools that are the default work a little differently. I’m willing to install Xcode, but before that maybe I can provide some information (such as version) about any particula

Re: Unable to build for Mac: adding ad-hoc signature failed

2023-08-09 Thread Dar Scott via use-livecode
Whoops, I sent the most recent before I saw that Panos had responded. Panos, yes, a build to the network drive with a minimal stack has the error. This minimal stack has a name of Test, no inclusions, no copy files. The drive provides SMB, AFP and NFS services. Dar > On Aug 9, 2023, at 5:55 AM

Re: Unable to build for Mac: adding ad-hoc signature failed

2023-08-09 Thread Dar Scott via use-livecode
I don’t know what I did. Building for Mac Intel works just fine. I’ll add my inclusions and such. I don’t have Xcode on this system. Perhaps there are some command line tools suitable that come with macOS. I still feel defensive that Mac said “detritus”. ;-) > On Aug 8, 2023, at 5:13 PM, matt

Re: Consumable In App Purchases on Android

2023-08-09 Thread panagiotis m via use-livecode
Hello Dan, The call to mobileStoreConfirmPurchase pProductID causes the purchaseStateUpdate message to be sent again with status=complete. So I would not suggest putting the call to mobileStoreConsumePurchase pProductID just after mobileStoreConfirmPurchase. You could either put it in a separat

Re: Unable to build for Mac: adding ad-hoc signature failed

2023-08-09 Thread panagiotis m via use-livecode
Hello Dar, I can successfully build a Mac standalone in a network drive. The error you are getting indicates that the app the standalone builder tries to codesign, has some extended attributes. This is strange, because the standalone builder does this very thing (i.e. it clears the extended attri