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.
Related
The app works normally when I set Settings>Accessibility>Display & Text Size>Larger Text to OFF or ON with default value.
However when I try to make the Text Size larger even a little bit, the app UI freeze at that moment,
My Home page includes UIRefreshControl, UITableView, UICollectionView. This issue is reported on iOS 14.6, iPhone 11 Pro Max & the standard version.
The app is built in Xamarin.iOS, using Mvvmcross framework
I have developed an educational app, and have built it with a storyboard of iPhone. It is working perfectly on iPad without a need for a change (except for pressing the 'X2' button).
Now that the app is active in App Store, I see that iPad users who search for my keywords, do not receive my app in their search results, unless changing the top menu from 'iPad Only' to 'iPhone Only'.
I am wondering if there is a flag that will set my app to appear in the search results for iPad users too.
Or am I forced to create another storyboard?
Will appreciate you help!!
There is no flag for that.
You can create a Universal App (meaning you do support both iPhone and iPad) which then will mean your app is listed in both iPhone and iPad searches on the App Store, however you need to also provide a UI for the iPad version too in this case!
I have found the answer to be: Targeted Device Family
When setting it for both iPhone and iPad, a different UI will be presented for iPad, and you should adapt it to appear correctly.
EDIT
As mentioned by #Lefteris, each target can be marked as universal for that same purpose, but Targeted Device Family exists in the project level and allows setting that flag for all target at once.
I'm still missing a practical guide for turning an iPhone app into universal: how to add a storyboard and how to turn a two-levels behavior (table -> data) into a split table view.
Recently, I have released a new version iPhone app, but as the following pictures, the back button of pages and the general button respectively have difference appearances in spite of the same iOS version(v8.4)
I must admit that I do not have deep understanding about iPhone app, and my iPhone app has been built on the Xamarin platform.
Does anyone know why this is occurred?
Back button
general button
Seems like the one device has button shapes turned on. This is an accessibility feature. If you can, check Settings → Accessibility → Button Shapes on that device.
I'm developing a custom keyboard app for iOS devices. After adding keyboard extension to my app I added a TextView to Main.storyboard and then I ran my app on an iPhone 5 simulator.
For adding my custom keyboard to available keyboards list I went to Settings > General > Keyboards > Add new Keyboard & here I added my custom keyboard but when I'm returning back to my app and trying to select my custom keyboard by long pressing the globe icon, my custom keyboard has not been shown there.
What's the matter here?
Please reply & I'm sorry for no code as I haven't coded any yet.
Thanks in advance
Please neglect the mistakes!
There is a bug concerning the simulator.
Either you run your extension on a real device or you can use the Photo app or Safari browser of the simulator to test your extension.
general article about developing iOS keyboards (head for “The Simulator”)
As of Xcode 6.1, you can no longer open 3rd party keyboards in most apps in the Simulator, including your own. (And not just 3rd party keyboards: most system keyboards refuse to show up, too.) Not only does this make debugging a whole lot harder, but it also prevents you from easily making screenshots of your keyboard if you don’t own some of the newer devices. This issue is marked as a bug in Radar, and seeing as how it first appeared in the Xcode 6.1 betas, I cannot fathom how it got through to release.
I have an app that was developed for iOS 4 and 5 and I migrated it to iOS7. When I test it on my iPhone 4 with iOS 7.1 is not showing the same results as the simulator.
Any suggestions?
Basically is not showing the initial segmented control, the map segmented control, the view associated with the control and it´s showing the scanner in a bigger size. The simulator showed the same issues before I restore the contents and settings in the simulator.
EDIT
If you watch very closely on the iphone it shows the segments and other elements of the view behind de navigation bar . But in the storyboard they appear right in the place that i want them. Is any form to consolidate my storyboard ??? Are any files that depend of the storyboard that i´m not including or generating.
The storyboard icon looks like black and also the .plist what does this means?
Simulator doesn't have the memory limitation as the device.
Simulator uses x86 arch, device uses ARM
It is a simulator, so it only "simulates" the behavior. Always test on device before submitting to the App Store.
Ok the problem was that i had installed the original app that is published in the app store. When I tested the current development on the iphone the existing app was replaced with the current one and that caused trouble. The solution was to delete the app from the device and then run again the current version of the app and that was all.