I have a problem with the Sidecar and Touch Bar feature of iPad and MacOS Catalina.
I can connect and see everything on the iPad including the Touchbar.
If I focus an application which is displayed on the iPad the Touchbar shows the corresponding Touchbar correctly.
After focussing an application on one of my other displays (MacBook or external HDMI displays) the Touch Bar does not update and change.
If I put that application on the iPad screen, then the TouchBar changes and shows the corresponding items.
This is really annoying when I am working with programming IDEs with nice TouchBar support. But I really don't want to put that IDE on my smaller iPad screen.
Is anyone else experiencing this and/or has a workaround?
Cheers
Related
I want to share a note in Notability app on my ipad as a white board for an online Zoom lesson.
For that I connect my ipad to my mac through cable, and mirror my ipad screen to my mac using the Zoom application's option of share of ipad via cable.
The ipad's screen is mirrored, namely, appears on my mac (usually, sometimes it doesn't and I have know idea why). However, the ipad's Screen Mirroring window (accessed via the ipad's control center) is stuck in a weird intermediate state: it keeps thinking and does not show any devices, but does show a Stop Mirroring button. In addition, Notability app in the ipad does not recognize the mirroring and does not enable the new presentation mode (but rather keeps showing the Send-to button instead of the display-mode button). For some reason, the mirroring occasionally does work fine, but usually it doesn't, and I cannot replicate what causes it to work.
How can this be fixed?
(My mac, ipad and notability are all updated: versions 10.15.4, 13.4, 9.3.1 respectively.)
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.
We're developing a web app that extensively uses Cavas 2D for some demos, and is successfully running on both iOS and Android devices. Recently we've added stand-alone mode for iOS devices, so user has to "Add-To-Home-Screen" and run it using screen icon, just like regular app.
What happens recently is that after 10-12 times we start the web app on iPhone4:
Status bar (initially set to 'black') suddenly turns white and we cannot exit Safari (by pressing home button).
If we try to make screen shot (home + power button), shutter sound is played as if screen shot was taken and saved.
If we try to lock the device (power button), screen turns black, but no action after that can bring unlock-screen or any screen for that matter - display remains black.
We can only do reset by pressing home + power for 10 seconds after this point.
If we do not lock the device, web app continuously work with no issues at all, it does not crash, but cannot exit it (double click on home button also has no result).
Has anyone experienced this with their web apps?
Any guidance in how to debug this would be highly appreciated. We've tried using Safari on OSX, connect iPhone to it and use Develop -> iPhone menu but no luck so far.
Thanks in advance!
I would start trying to debug by running XCode with the iPhone connected to the computer.
In XCode open "Organizer" and go to the tab "Devices".
You should see your device there, from which you can view the iOS console. That might be able to tell you what is going wrong with the phone stops responding.
I don't think you have to put the phone in development mode (or be a paid developer) to see the iOS console.
I'm trying to get an external screen for an iOS iPad app up and running. Currently I just could test this with the iOS simulator (VGA connection kit is on it's way).
My problem is that when starting the app in landscape (left or right) or portrait upside down the external display remains black. If started in normal portrait mode then everything is fine.
You can test the whole thing with the sample project provided by Apple. It works in 1 of 4 cases (see below) and behaves exactly like my project:
https://developer.apple.com/library/ios/#samplecode/ExternalDisplay/Introduction/Intro.html#//apple_ref/doc/uid/DTS40010724
Steps to reproduce the problem:
Start your iPad 6.0 simulator by hand (not via Xcode, run project).
In the menu bar: Hardware > TV-Out - pick a screen resolution. A second window will appear and act as a second screen.
Turn it via CMD+ArrowLeft/Right to landscape-left/right or portrait upside down.
Now run the project in your iPad 6.0 simulator.
If the application has started (don't worry, this app just was not designed by Apple to rotate its interface correctly) press the button in the navbar.
-> The second screen will remain black.
Same test in protrait mode (will work correctly):
Quit the simulator, repeat steps 1,2,4,5, don't turn the simulator, leave it in normal portrait mode.
-> The second screen will be filled.
Now I wonder why that is. It's not very nice to only have the second screen at hand if the app was started in portrait mode. And it's not very pleasant to develop and test with this problem.
Funny thing is that whenever you start the app in portrait mode it works, but if you start it once in an other orientation it won't work anymore till you restart the simulator.
Maybe you can also tell me if this is also a problem with the real device and a connection kit / airplay.
Concrete questions:
- Is this bahaviour of the simulator normal?
- Did I just forgot something?
- Is this problem just occuring in the simulator and not with running apps on devices connected to a seconds screen?
Thankful for any hint or advice!
Problem has solved itself. With the newest versions of Xcode/iOS Simulator it works as expected now. The code iteself was ok, just the Simulator did not handle everything like it would happen with a real device.
One of our clients has come back to us today with a bug that has been found on the Torch 9860 (running OS 7.0).
It seems my app is running in a small box in the centre of the screen, with a big blue border surrounding it. If the soft keyboard is not showing, there is a black box where the keyboard would be.
This issue has not been reported before on other devices, and the app has been "in the wild" for a while. I have not seen it on our test devices - but do not have a Torch 9860 to test with.
I have attached photos of the app running on the device. The blue border is the problem - normally my app would fill the whole screen. I did not create the blue border (to the best of my knowledge).
Apologies for the photos - this is what they sent to us.
Showing the app running in a small box surrounded by the blue border. Note the black space where the keyboard would be if it was required.
Showing the app with the soft keyboard visible.
With some googling, I found 1 possible reference to this issue to do with an instant messaging app not showing correctly on 9860. Feedback was that they were looking into it.
I wonder who else has seen this, or can recommend solutions?
Updates
runs fine on the 9860 emulator
seems to be mentioned in this thread: Blackberry OS 7 Compatibility failed with 9860/9850 device
Thanks, Rafael (left answer in a comment to my question).
Based on the comment I told the client to run the app in compatibility mode (accessed through the system options - application options menu). This seems to have fixed the problem without me having to recompile for SDK 7.0 (also I don't have to start supporting multiple OS's yet).
I already had the blackscreen on bottom when the keyboard should be popped. But it happened rarely and get resolved with an update of the Blackberry
Ask for the OS version/platform of the Blackberry, and propose a update to him, if available.