Dave Nottage

..and its name is? It may help in finding what the problem is from the logs. Better still, what is the package identifier? Is the app on the Google Play, and if so, is it available in all regions?

If you have not seen already, Chris Pimlott appears to have beaten me to it: https://fmxnative.com/ios-extensions-with-firemonkey

You mean it's possible to use an extension of the type you're using in a Xamarin project? Can you find out what their build process does? I'd like to be able to help you solve this. Can you confirm that the extension you created is exactly the one I asked about earlier? i.e.

Firebase covers a broad range of subjects: https://firebase.google.com/ Which one(s) are you referring to?

I guess you mean whether it is in Light or Dark mode? If so, take a look at GetUserInterfaceStyle, here: https://github.com/DelphiWorlds/Kastri/blob/master/Core/DW.UIHelper.iOS.pas

Yes, it was a "Dave" bug. Updated demo attached - now allows you to set button type, style and corner radius. AppleSignInDemo.zip

Has not been successful so far. The initWithAuthorizationButtonType method seems to ignore the 2nd parameter being passed to it, as well as the setCornerRadius method. Very odd

I'll see if I can debug it, thanks

Ah yes, sorry.. the roundness can be changed. I'll take a look at adding that. These are the style values: ASAuthorizationAppleIDButtonStyleBlack A black button. ASAuthorizationAppleIDButtonStyleWhiteOutline A button with a white outline. ASAuthorizationAppleIDButtonStyleWhite Which are displayed in the link I gave: https://developer.apple.com/design/human-interface-guidelines/sign-in-with-apple/overview/buttons/#creating-a-custom-sign-in-with-apple-button I'll also take a look at adding support for those.

The implementation I have done uses the native control, i.e. ASAuthorizationAppleIDButton, which is fairly limited in the styles available. Please refer to: https://developer.apple.com/documentation/authenticationservices/asauthorizationappleidbutton?language=objc https://developer.apple.com/documentation/authenticationservices/asauthorizationappleidbuttonstyle?language=objc If you have a sign-in button which does not have a style that is mandated by Apple, your app is likely to be rejected. See: https://developer.apple.com/design/human-interface-guidelines/sign-in-with-apple/overview/buttons/#creating-a-custom-sign-in-with-apple-button Examples of rejections: https://community.auth0.com/t/apple-store-rejected-app-because-of-sign-in-with-apple-styles/43854 https://github.com/firebase/FirebaseUI-iOS/issues/823 For these reasons, I'm not going to be implementing styles other than what they provide.

Sorry.. been busy with Memorizor. They're still coming. Were you after an installable component for Apple Signin, or something else?

For anyone that might come across this topic: I had this error recently. It was being caused by the less than optimal Version Info grid in Project Options. Somehow the CFBundleExecutable value was changed: So if you have the same error message, it might pay to check the values in the Version Info section

I figured this would be easy.. I'm working on an app that needs to read data from a com port - this I have code for. I'm having trouble finding something (that actually works), that can "simulate" data being sent to the port so that it can be read from the app. Simulation is needed because I'm remoting to the machine in question and I'd rather avoid having to (or for someone else to) go to where the machine is to connect a device that might not even be suitable. I have come across this: https://www.aggsoft.com/com-port-emulator.htm, however I'm unable to work out exactly how it is supposed to emulate (when clicking "Start", it prevents anything else from accessing the port) or it's just not suitable anyway. I used to work on apps over 20 years ago (using Delphi 3) that did this kind of thing, but we had the luxury of having the actual hardware with us. That's about how long it has been since I've done this kind of thing.

Com0Com works great, thanks! I'm using it on Windows 10. Thanks also to everyone else for replying

Looks more like a fix for: https://quality.embarcadero.com/browse/RSP-23095 Two birds with one stone (perhaps unintentionally)?

In the Entitlements section of the Project Options, ensure that "Secure File Sharing" is checked.

That the export option exists had slipped my mind.. I'll update my article; thanks!

You'll find you won't be able to debug with a device that has iOS 14.0. Deploying will work; just not debugging. Because Delphi does not import the iOS 13.6 SDK correctly, either (as well as iOS 14.0). Use iOS 13.5 SDK if you can - it comes with Xcode 11.5. I wrote about it here: https://delphiworlds.com/2020/08/using-a-prior-ios-or-macos-sdk-with-delphi/

Sorry, I remember now that I did not obtain them from there. Trouble is: I cannot remember exactly where I obtained them, however I've now added them here: https://github.com/DelphiWorlds/Kastri/tree/master/ThirdParty/OpenSSL/1.0.2o/iOS

https://github.com/IndySockets/OpenSSL-Binaries/blob/master/OpenSSLStaticLibs.7z

I expect you'd need to patch the TBaseWebViewDelegate.AuthenticateForHost method in FMX.WebBrowser.Delegate.Cocoa unit, and pass the username and password instead of using TDialogServiceAsync.InputQuery. I'd recommend submitting a feature request in the Quality Portal for an OnAuthenticate (or similarly named) event to make this easier.

I've already answered your email, but for the benefit of others: On iOS, you can check what the user has authorized with: TCLLocationManager.OCClass.authorizationStatus which will return one of the following values: kCLAuthorizationStatusAuthorized = 3; // User has authorized location services ("always" on iOS 8+) kCLAuthorizationStatusDenied = 2; // User denied authorization for your app, or they turned off location services in the device settings, or the device is in airplane mode kCLAuthorizationStatusNotDetermined = 0; // App is yet to request permission for location services kCLAuthorizationStatusRestricted = 1; // User is unable to authorize location services due to restrictions such as parental controls kCLAuthorizationStatusAuthorizedAlways = kCLAuthorizationStatusAuthorized ; // See kCLAuthorizationStatusAuthorized kCLAuthorizationStatusAuthorizedWhenInUse = 4; // User has authorized location services only when the app is in use (from iOSapi.CoreLocation unit) If your app needs location services and the status is kCLAuthorizationStatusDenied, you could present a message asking if they would like to change the settings, and if they do, execute OpenSettings: uses Macapi.Helpers, iOSapi.Foundation, iOSapi.UIKit, iOSapi.Helpers; function UIApplicationOpenSettingsURLString: NSString; begin Result := CocoaNSStringConst(libUIKit, 'UIApplicationOpenSettingsURLString'); end; procedure OpenSettings; begin TiOSHelper.SharedApplication.openURL(TNSURL.Wrap(TNSURL.OCClass.URLWithString(UIApplicationOpenSettingsURLString))); end; This will take them to the Settings app, and show the settings specific to your app (there may be a little delay in it changing to the settings for the app)

I've been using it for the past few days. The main issue at the moment is that Delphi does not import the iOS 14 SDK correctly, so it cannot be built against. Related issue: debugging on an iOS device with iOS 14 is hosed. Deploying works, debugging does not.

You appear to have 2 certificates on the Mac that are the same. Perhaps one is expired. To check this, on the Mac in Applications/Utilities, run the Key Chain Access app, ensure that expired certificates are listed by clicking Show Expired Certificates in the View menu, and select login in the Keychains list, and My Certificates in the Category list: For any expired certificates, right-click them and click "Delete"

The bundle identifier needs to match the identifier given to the App Id that was created for the application on the Apple Developer website, e.g I created this one for testing Firebase Cloud Messaging (for myself - you need to use your own): The convention is to use reverse domain notation (if you have one), or at least something that should be globally (literally) unique. This is also the App Id that you would have enabled Push Notifications for: