Dave Nottage

Changing CFBundleDisplayName works OK for me. Here's my steps: 1. Create a blank FMX project 2. Save it as: Fred 3. Compile/Deploy to iOS device - it appears as "Fred" 4. Change CFBundleDisplayName from $(ModuleName) to: Bob 5. Compile/Deploy to iOS device - name changes to "Bob"

Looks like you'll need to file an enhancement request, at: http://quality.embarcadero.com The later answers at this link: https://stackoverflow.com/questions/5907369/file-upload-in-webview Have suggestions as to how it should be implemented; the important part being that the WebView descendant needs to implement openFileChooser.

Please email Calvin Tang at Embarcadero. His email address is the usual pattern, i.e. firstname.lastname@embarcadero.com

A reproducible test case might help.

I wouldn't rely too much on a repo that infringes Delphi source copyright

Not entirely obvious from the FAQ etc: does TestInsight have some method of running tests on the device (or Mac machine) that are reported back to TestInsight in the IDE? Sorry if that's a stupid question 🙂 It may also be what Darian is interested in.

What might those adjustments or extensions be?

As far as I'm aware, yes, however it seems Apple has relaxed the requirement until January: https://www.macrumors.com/2019/09/03/apple-macos-catalina-notarization-mac-apps/

Without a reproducible test case, it would be hard to tell. Some prudent adding of Log.d calls and use of the Console app (in /Applications/Utilities) might help find where it is crashing.

Incorrect: https://help.apple.com/itc/apploader/#/apdATD1E53-D1E1A1303-D1E53A1126

Without seeing all the code, it'd be hard to determine what is causing the issue.

On Android, TPath.GetDocumentsPath is, and has always been, the sandboxed (i.e. app specific) documents folder. If you wish to access the shared documents folder, it is TPath.GetSharedDocumentsPath. Prior to Delphi 10.3, the targetSdkVersion being used in the manifest was 19. In Delphi 10.3 the targetSdkVersion is now 28. From API level 21, applications that need permission for external storage (which is what TPath.GetSharedDocumentsPath points to), need to request permission at runtime. For an example of how to do this, take a look at this demo: https://github.com/Embarcadero/RADStudio10.3Demos/tree/master/Object Pascal/Mobile Snippets/ShareSheet Specifically in the TShareSheetForm.btnTakePhotoClick method in uMain.pas where permissions for external storage are requested. You don't need to request permission for TPath.GetDocumentsPath, so I have no idea why that folder is not working for you. Are you attempting to access files that are being deployed there (i.e. they have entries in Deployment Manager)?

You're naming the labels as (for example): 'LabelTwo'+TButton(Sender).Name but you're calling FindComponent as: FindComponent('LabelTwo'+TButton(Sender).Tag.ToString) When it should be: FindComponent('LabelTwo'+TButton(Sender).Name)

I'd be more interested in how these are being created and free'd.

As long as it's just the background processes of the application you're interested in, you could use: https://developer.android.com/reference/android/app/ActivityManager#killBackgroundProcesses(java.lang.String) Since Android 2.2, you cannot close the entire application. You would probably do something like this (untested): uses Androidapi.JNI.JavaTypes, Androidapi.JNI.GraphicsContentViewText, Androidapi.JNI.App, Androidapi.Helpers; procedure Kill; var LService: JObject; begin LService := TAndroidHelper.Context.getSystemService(TJContext.JavaClass.ACTIVITY_SERVICE); if LService <> nil then TJActivityManager.Wrap(JObjectToID(LService)).killBackgroundProcesses(StringToJString('com.whateverpackagename.itis')); end;

What did you change the locations to?

You need to call Intent.setType with an appropriate type for email, e.g. plain/text message/rfc822 application/octet-stream If that still does not work, then there's probably no email client installed.

You have not added the MessageUI framework correctly, since it is appearing in "Other Paths", rather than "Frameworks". Please remove that entry and: Select an existing framework listed in the "Frameworks" section - this will ensure that none of the radio buttons are selected when the Add Remote Path item dialog shows Click the Add button In the Path on remote machine combo, enter: $(SDKROOT)/System/Library/Frameworks In Framework name, enter: MessageUI Click OK Click Update Local File Cache Click Save

You'll need to show the code that's linking to the MessageUI framework. I expect it's attempting to link to MessageUI.tbd when it should be just MessageUI (i.e. no extension), and/or you've added the framework incorrectly to the SDK.

I think that may be how I did it. I was unable to locate my old code.

Come to think of it, I did something like this back around the XE3 era and like you had to fight with it to make it work. Sadly, I may not have the code any more, but I'll take a look later just in case.

I'm using a VirtualBox VM with Android x86 ISO installed on it, which has the ability to bridge to ARM (using libhoudini). See my earlier replies.

You use a logcat viewer to view the logcat messages coming from the app. I have one called DeviceLens, which can be found here: https://github.com/DelphiWorlds/MiscStuff/blob/master/Test/DeviceLens.zip You may find that the Processes list does not populate (still bugs to iron out), however you should be able to press the "Play" button and watch the messages, as well as filter on text or the application package name (type it in to the package name edit and hit enter). In the Android VM, if you go to settings, there may be an entry named Android x86 Options (just after the Sound option). Tap that, then enable the Enable native bridge option (i.e. bridge from x86 to ARM). Then run Terminal Emulator (still in the Android VM) and run the following commands: su /system/bin/enable_nativebridge If you don't have the Android x86 options in Settings you may have to install a later Android x86 ISO. I used the latest available, from here: https://www.android-x86.org/ Sadly after doing all that, it still would not work for me. The app doesn't get past the splash screen, however it also does not crash. It might turn out different for you (I use VirtualBox)

If the IDE can "see" the device, are you able to use a logcat viewer to determine what the crash is?

What library are you using? Perhaps I can find a solution for you