FireMonkey XE5 Icons for iOS app - delphi

I have an iOS app developed in FireMonkey XE5 (Update 2) and I have set up all the application icons for the iPad (as found under project options). When running on an actual device, the spotlight search icon always uses the default FireMonkey icon.
I have looked the the deployment options and removed the default icons, but they are been added automatically.
I have added spotlight images for the iPhone settings (even though I am running this on an iPad), but this did not help.
I have replaced the default spotlight images in the bin/Artwork folders with my images and this did not help. I guess if I replace ALL default images in iPad + iPhone folders I will solve my problem, but this will not work if I am developing a second application.
Has anyone experienced this problem with Delphi FireMonkey applications? Any suggestions on what will work to solve this for all projects?

Related

Why is my React Native app icon showing up with distorted colors on iOS?

I checked my asset and it has the right color, but the colors of the icon in the iOS folder are wrong. I used expo prebuild to create the iOS and Android folders, has anyone else had this issue? I cannot find any questions about this online and I have no idea what the issue is. The first image is what the icon should be, the second is what it is showing up as. The app target in Xcode also shows this strange version so I think it's an issue with react/expo. I have not tested on Android yet to see if this is also an issue there.
NOTE: The colors behind the iOS icons are different because the apps are on different parts of the home screen. That is not part of the issue.

launch screen cannot be changed with Delphi 10.4.2 for iOS iPhone APP

I am developing an iOS APP by Delphi 10.4.2. The PAserver 12.2.10.3 on BigSur.
I can modify the icons by my own pictures, but the launchscreen picture is always the Delphi torch.
I checked the deploy file list, as shown in the fig. It seems no iPhone launchscreen being added? Not sure where went wrong. wondering if there is any resolution requirement for the launch picture?
Help needed. thanks,

iPad Pro. Disable native 2732‑by‑2048 resolution

Need to disable the iPad Pro native 2732‑by‑2048 resolution for my app.
I found that it was auto activated if the app use a Launch Screen(LaunchScreen.storyboard).
Is there a way to disable iPad Pro and continue to use Launch Screen.
(I'm surprise that even with no icon for iPad Pro, the native mode was activated, i'm sure a lot of dev don't have the app ready for this)
Thanks
Are you using LaunchScreen.xib or LaunchScreen.storyboard? If so, if the version of Xcode you use supports the iPad Pro, it will compile the LaunchScreen for everything Xcode supports.
You could use an older version of Xcode which does not recognise the iPad Pro as you don't need it.
Or you could use Images.xcassets and not provide an iPad Pro launch image, though according to what you're asking, this doesn't seem that suitable. You could always use the LaunchScreen.xib/storyboard as the initial storyboard, so as far as the app is concerned, you're using LaunchScreen.storyboard instead of Main.storyboard. Though not providing an app icon should hold all this back, as it does with my current apps. Perhaps file a bug report with Apple? Hope this helps!
Official answer from Apple:
If an application includes a launch storyboard and is built with Xcode 7.1 or later, that application will run at native resolution on the iPad Pro regardless of whether the application includes a 167x167 icon.
If you would like to see this behavior changed in a future version of iOS, I suggest you file a bug report. Bug reports can be filled by visiting http://bugreport.apple.com.

Xamarin App Keyboard is a different size to iOS Keyboard

I'm developing an iOS app in Xamarin (not using Forms, using Xamarin.iOS) and I have noticed that the keyboard which appears in my Xamarin built app is larger than Keyboards which appear in other apps.
E.G. My app
E.G. Other iOS app (Apple Notes)
The numbers aren't really important, what is important is that there is definitely a difference in size between the two keyboards in terms of key height and key spacing.
There does not appear to be any obvious options or settings surrounding this. Trying different Keyboard Styles (I'm using "Default") does not solve the problem.
I would like to get my Keyboard to be the same size as a normal iOS App Keyboard.
EDIT
Krumelur's answer is correct.
This is how I specified the launch screens
https://stackoverflow.com/a/25960203/807836
In Visual Studio, there does appear to be an issue with this XML entry being lost if you edit the project file through the IDE.
This is not Xamarin related. Your app is running in compatibility mode on an iPhone5 or 6. You will have to provide a launch screen for the particular device or a launch image to let iOS know you support the bigger screen.
See here on how to use launch screens.

Wrong Icon Installed by Xcode

I have been pulling my hairs for the past few days. It appears I am the first one who has experienced this problem because I could not find anything that is even close through Internet searches. The problem that I have experienced is the following:
Icon for retina iPad of iOS 6.1 and prior (size 144x144) and Icon for iPhone of iOS 7 (size 120x120) are not installed correctly. If I use asset catalog, when installing my app on iPad (retina) with iOS 5, the iPhone icon (120x120) is installed. iPhone with iOS 7 works fine using the same icon (120x120). If I don't use asset catalog, but instead add the icons to the info.plist (CFBundleIcons array), it goes the other way around. iPad icon is fine this time (144x144 icon was installed). But iPhone uses the iPad icon (144x144).
What's more strange is that this is not a problem with one of my two targets. It is only a problem for the second target. The second target was created by duplicating the first one. I have compared the info and settings of the two projects, but did not see any difference (other than bundle identifiers and product names etc., of course).
I've upgraded my Xcode to 5.0.2 and that makes no difference.
I'd appreciate it if anybody could shed some light on this.
Update #1: I tried to use the icons from the first target and the problem is still there. So it's not related the icon png files. It's target related. Also tried to clean the project, delete the app from the devices to no avail.
Update #2: When I use plist instead of asset catalog, what's (incorrectly) installed on my iPhone (iOS 7) is not the 144x144 icon. It is 144x144 icon for iOS 6.1 and prior. It's still an incorrect icon.
Update #3: This is actually easy to reproduce. I created a cocos2d project from scratch this time (the Hello World project). Tried to add all the icons using the two ways introduced in the following technical article from Apple:
https://developer.apple.com/library/ios/qa/qa1686/_index.html
When using the asset catalog, 120x120 icon was installed on my iPad (retina) with iOS 5.
When using the project editor, 152x152 icon was installed on my iPad (retina) with iOS 5.
In both cases, what is supposed to be installed is the 144x144 icon. Will probably contact Apple on Monday.
I filed a tech-support case with Apple and confirmed that this is a known issue (as of 02/10/14). I open a bug report with Apple. This issue is not noticeable for most people because icons are all resized from one design. Even though the wrong icon is installed, it is barely noticeable (the icon is still resized to to the correct size on the device automatically). This is noticeable when you want to use different icon design on different iOS. For example, the icon curvature for iOS 7 is different. There is no workaround according to the Apple support.
Hope this is useful for anyone who runs into the same issue.
Regards,
Ryan
Make sure you don't have the older icons named with the an older version of Xcode's default icon names (Icon.png, Icon#2x.png, Icon-72.png). I have found that when these names exist, they are used even if other icon names are specified.
Try cleaning the project. Command-Shift-K , that usually fixes such issues

Resources