I ve been getting some reviews on my app about a freeze on the right side of iPad keyboard. I did not even know that could be possible?
Does anyone experienced anything similar?
Any help on this keyboard freeze problem would be really appreciated cause I m little bit lost.
The "right side" of the keyboard is probably a red herring.
There are only two ways you could interfere with keyboard input:
Your input field is rejecting certain characters, but not giving user feedback that you're rejecting them.
You are doing some long-running work on the main thread (like downloading data, reading to/writing from disk, etc.) If this is the case, move it to a background thread.
No it's not readily possible from what I know, due to the strict permissions of the iPad and apple in general it would not be possible for an app to do this without you intentionally "hacking" the iPad. The only thing i could suggest is that the users are downloading malware to the iPad unwittingly through the site that you have made your app available ??
Related
I am new to iOS development and wondering if it's possible to create a floating button which always stays on top of screen even if you have any other app running in full screen mode?
No you can't do that on iOS, Apple isn't allowing this kind of features (like Messenger on Android for example)
I assume you mean something closer to AssistiveTouch. When turned on in accessibility, it will stay on top of the screen, no matter what app you have open. I recommend reading the Apple Docs for further investigating into this, but at the moment, Apple does not let you do this. Your app can't mess with other apps. It's pretty against what Apple's design guidelines allow you to do.
Is there a work around for what you are trying to accomplish with this? Maybe if you expand your question, I can help.
This is a quite strange behavior that 'persecutes' me since iOS 7.0 :) I hope someone of you can help me this time! As you probably know when you are using VoiceOver your gestures are totally different from the 'normal way'. When you need to bypass VoiceOver for a specific view you can set its accessibility traits as UIAccessibilityTraitAllowsDirectInteraction. When the view has this parameter set the user can interact with it as usual (like VoiceOver is not active in that particular view).
Quite often happens that this ability is randomly lost so VoiceOver acts in its normal way.
Did anyone of you encounter this problem in its experience? Did he solve it? Fortunately turning off and on VO seems to temporarily solve this issue (until next time it happens again)
Any idea? Thank you very much
I've seen this with other things as well. For example, notifications can be spotty, particular Screen Changed or Content Changed notifications. I believe this happens as a result of turning VoiceOver on and off. For example, if you were to turn VoiceOver on, leave it running, and open your application as a user would, you would never experience these issues.
However, if you use the VoiceOver shortcut. Or interrupt the application, re-install, and restart while using Xcode, you can disrupt the VoiceOver's connection to the application. It doesn't bond correctly. So, simple things like navigation work fine. But advanced features like notifications (and perhaps some of the more complicated traits) don't work.
Essentially, I would classify this as a bug, but a bug that only shows itself when you use VoiceOver in a way that only a developer would use it.
I want to make a couple buttons on my iPhone to control my stereo. I thought I might be able to do this by putting a couple webpages on my homescreen that issue stop, play, next, etc requests to my media server that quit shortly after being opened. Is there a way to tell safari to quit other than crashing it? If not, what's the best way to crash safari? I realize this isn't very elegant, but I really want to have buttons on the homescreen, not in an app, and this was the best solution I could come up with.
I realize I could make the buttons native apps, but I don't want my iPhone running any third party software, even from myself (I have very little iOS programming experience, and even though I'm pretty sure there's a lot of sandboxing/this is trivial, I'm worried I'll mess up my phone). If you think I shouldn't worry about that and think it would be better to make these buttons native applications, or have any other suggestions, please let me know.
Not only is there no need for your web clips to be closed - just issue the command once - crashing Safari is a bad idea at best.
Is there any way to distinguish in the iOS app a situation that someone have changed volume by hardware buttons on iPhone/iPad from the situation that it has been done by some UI control in the app?
I have searched for that and so far I came up with many ways to be notified that the volume has been changed but there is no way to find out whether it was done by the UI control or hardware buttons. Notifications include info abut a reason of change but it is the same for both situations.
After a long search I came up with this:
There is no way to detect hardware button been pressed (so far iOS 7). You can only be informed with the result - volume changed. It means that the only solution will be to properly handle situation when the volume change is triggered by some UI component.
You might want to have a look at the private API. rpetrich did some research again.. :) click here
But you need to know that this is not really a good idea because apple probably will reject your app when accessing private apis.
I've observed that if I change the device language, and after coming back to home screen, all background processes quit themselves. If I click on a running app icon again, it starts from scratch -- i.e., from application:didFinishLaunchingWithOptions:.
Am I wrong somewhere? What can I do to work around this?
I think this is a nothing odd and a default behavior.
You may want to look into this post if you want to make changes right from inside your application, though I am not sure on how good this is, as I have not personally implemented it.
language change only after restart on iphone
Let me know if you need more help.
Hope this helps you.