Converted an application using Android WebView as a wrapper for a Mobi site, this weird issue has occurred:
The app can scroll, only after rotating the view does it correct and still then it is only some of the time, additionally the issue can be presented when rotation is done if there was no issue before.
Tested Operating System:
Simulator
BB10.2.0X.1803 -> BB10.2.1.1925 (Occurs in all builds between)
BlackBerry Devices:
Z10 and Z30 running 1925.
I can provide more images if required.
Thank you in advance.
After awaiting a response from BlackBerry I have heard nothing so it is not confirmed that this will fix every issue with BlackBerry 10.2 devices and WebViews however it sure has resolved my issue.
The WebView appears to render incorrectly due to hardware acceleration being enabled on Android to BlackBerry applications, the solution to this problem is to disable hardware acceleration in one of two places.
if (Build.BRAND.equals(BLACK_BERRY))
{
webView.setLayerType(View.LAYER_TYPE_NONE, null);
}
Assuming that you have a WebView that is defined as webView, else deactivating the setting in the Android manifest for the entire application is also a feasible solution.
<application
android:hardwareAccelerated="false"
This either one of these should solve the issue with the WebView.
Related
I started porting my iOS app (which works on iPhone and iPad) over to Mac via the Catalyst route but WKWebView is behaving very strange. All the content is too small, it looks like it thinks the monitor is 2 times bigger.
The website I am displaying is responsive and works correctly on iOS devices as well as a Mac in Safari. On iOS it looks the same in Safari and WKWebView but with Catalyst and Mac Safari, the Catalyst version is much smaller.
I also tried this with Google.com and the issue is the same.
Anyone knows what might be happening? Since this doesnt happen just to the single site, I guess the issue is with WKWebView?
Are you using the Mac or iPad idiom for your Catalyst app? The “iPad” idiom, which is the default (and only option for apps that support Catalina), will downscale your entire app to 77% it’s original size. Read more here: https://developer.apple.com/documentation/uikit/mac_catalyst/choosing_a_user_interface_idiom_for_your_mac_app
My guess is that your app is being downscaled, including the web content. You could fix that by switching to the Mac idiom. If that’s not an option for whatever reason, maybe you could try scaling the web content back up with CSS?
I have an app that is built with PhoneGap. One page in the app copies the contents of other page's canvases as images. This worked fine on older versions of iOS, but recently I noticed that the copied canvases are sometime blank. The rest of the page is rendered correctly. I don't know which iOS version it crept in, but I'm currently running iOS 10.3.1 on my iPad Pro. This does not happen when the same code is running as a WebApp in mobile Safari (or Chrome, or on my Mac laptop browsers).
Using the debugger on the App, I can restore the page by simply toggling the display property. This indicates to me that it's a rendering bug in the built-in Webview that Cordova uses. I currently have a patch that toggles the display property. This works, but it causes flickering even with requestAnimationFrame() or SetTimeout(fn, 0).
The app is built with cli-6.5.0 using PhoneGap Build.
Has anyone else seen this bug or have a better patch?
Follow up:
Toggling visibility fixes the flickering. When the problem occurs the canvas behaves like it's not visible, but the DOM reports that it is. Also the problem seems to occur when the canvas is copied under an Ajax callback. Delaying the processing with setTimeout() does not solve the problem.
I have searched around on here, but couldn't find anything to answer my question. I have developed a custom app for the iPad; it involves using a set of PDf documents that change pages based on a 1 second time frame. To achieve this is have used the 'PDF Reader Core for iOS' external library. Please find the link here: https://github.com/vfr/Reader
The app works perfectly fine on the actual iPad, however I also wish to run the app on Mac Mini Machines, so the obvious thought I had was to boot the project in the iOS Simulator on the machines (saves me recoding it for OSX.). Now, here is my issue. The app works pretty smoothly in the simulator, the only issue I have is that there is a slight render lag between the page change on the Simulator. It isn't at full resolution, and appears blur whilst it renders, however the time frame to change is so quick that the simulator doesn't have enough time to render to full resolution. I have also emailed the developer of the library and he provided some suggestions however, these didn't seem to fix the issue.
I am aware that this could be to do with the actual PDF Reader itself, however I wanted to ask if anyone had any suggestions if this could be fixed in regards to the iOS Simulator? Any way to speed up the simulator?
I am using OSX Yosemite, Xcode 6.4 and Objective-C.
It seems at this moment i may have to recode for OSX. Any suggestions would be highly appreciated.
Thanks
I am currently building a sencha touch 2 application and trying to deploy it on iPad. I am working on "mac OS Snow Leopard" and trying to deploy my app on an iPad2 with iOS 5.1.
After having some issues building and deploying the application, that I managed to fix thanks to this post: http://www.sencha.com/forum/showthread.php?192946-2.0.1RC-Native-build-seem-to-be-broken ; I seem to have a new problem with orientation.
Indeed, even with a specific "landscapeLeft" orientation configuration given in my 'packager.json' file, both iOSSimulator and iOS launch the app in landscape mode, but as soon as the sencha logo is gone my view goes to portrait mode and get stuck in this mode. When I do an Ext.getOrientation() I get 'portrait' as an answer all the time, whatever the orientation of my device is.
No exceptions or console messages are launched and after having visited a lot and a lot of posts I haven't found anything really addressing my issue. the closest one I found was this one: http://www.sencha.com/forum/showthread.php?151238-landscape-gt-portrait-orientation-how-does-it-work-now, but with sadly no effect.
I'd also like to keep the native build of sencha and avoiding phonegap if possible.
has anyone encountered the issue, or have any idea on this problem? I am quite lost and need to fix the issue as quickly as possible.
Thanks.
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.