I am getting a weird black edge around clickable items in the android emulator
when testing in release mode. Also happens on devices when deployed.
problem was I needed to update my JDK...or at least I think. If you come across check for java updates.
Related
I have an issue with Xamarin , when one day your Xamarin Android app works perfectly, then precisely this happens:
You send it to the store. And add keys: <uses-sdk target=27 min=23>
App gets released in the store, but now it has peculiar UI issues
All things that have had rounded corners or were circles, thank's to OutlineProvider, became rectangular.
If you try and run your app in Genymotion emulator, app has about 10 fps, and the log constantly tells you that you are doing too much work in the wrong place.
Yes , and preceding all these events was an update of macOS to Mojave.
I'm really wondering if anyone has come over this situation with Xamarin Android, when one day your app is all right, and the next, it is all screwed up, without any observable reason.
The problem was, that I have placed my <uses-sdk> tag in the manifest under the <application></application> tag.
Background
I have a live wallpaper that uses the relatively new API (from Android 8.1 - API 26) to request the OS to use customized colors:
https://developer.android.com/reference/android/service/wallpaper/WallpaperService.Engine.html#notifyColorsChanged()
https://developer.android.com/reference/android/service/wallpaper/WallpaperService.Engine#onComputeColors()
The problem
On Android 8.1 and even on Android P DP1, all worked fine with these functions, as they did what normal wallpaper do with the colors, affecting the notification drawer if the color that was chosen is dark enough. Here's a comparison between choosing a non-dark color and choosing a dark color background:
Thing is, on Android P beta (DP2), even though this function get called, it doesn't do anything, ever.
To test it on your own, you can try the full project I've published here.
What I've found
I thought that maybe the API has changed, so I've tried to find which functions are available, but I couldn't see anything that's new.
I've tried to use various ways to return the customized colors:
a. WallpaperColors(Color.valueOf(0xff000000.toInt()), Color.valueOf(0xff000000.toInt()), Color.valueOf(0xff000000.toInt()))
b. WallpaperColors.fromDrawable(ColorDrawable(0xff000000.toInt()))
c. WallpaperColors.fromDrawable(BitmapDrawable(completelyBlackBitmap))
d. WallpaperColors.fromBitmap(completelyBlackBitmap)
Sadly none worked (fromBitmap is the one that works well on Android 8.1).
Seeing this, I've re-checked that my code is ok, and noticed that the built in live wallpaper works fine, and that selecting a solid black wallpaper (instead of live wallpaper) also affected the UI of the OS.
Seeing that it works with built in apps, I've reported to Google about this issue, only to find out that they don't understand what I'm talking about, and each time I've tried to tell them they've misunderstood it differently:
https://issuetracker.google.com/issues/79404938
https://issuetracker.google.com/issues/79665215
https://issuetracker.google.com/issues/80029770
I wanted to make sure it's not an issue with just my app, but with others too, so I've tested Muzei live wallpaper app, which is actually made by one of Google's own developers. The issue indeed occurs there too, while working fine on Android 8.1.
I was just curious, and wanted to check if the issue could occur if I've moved Muzei to be a system app, but after doing so, I've seen the issue still exists.
The questions
How come it doesn't work anymore?
Is there a workaround/fix for this?
Why does it work fine for built in apps and for normal wallpapers, but not for third party apps? I don't think their code is any difference.
OK, Google confirmed it's a bug, which will be fixed on later version:
The development team has fixed the issue that you have reported and it
will be available in a future build.
And, it works fine now on DP4 (beta 3) of Android P.
Have a most bizarre issue that just started happening two days ago for no reason. It seems to be getting worse too. I remote into my home computer routinely to develop my cordova app. Connected to my computer is a Samsung phone for testing. After compiling my app to the phone, i launch chrome inspector to see the app and do debugging, UI development, etc
I have been doing this setup for 3 months now and it all works fine. About two days ago when I compile my app chrome inspector is just showing blank - it says its loaded the project/index.html file - but everything is blank. No resources, no elements...nothing. However when I compile and deploy the app to the device, I see the "app name" in Chrome disappear and reappear after that attaches and deploys...I then click the "app name" to open it up in Inspector. So Chrome see's it deployed, but inspector is just completely blank.
I recompile, redeploy and then it works again. But more and more lately, even after recompile/redeploy its showing blank again. I have no idea whats caused this - I didn't do any updates or plugin changes....I was literally testing CSS values when all this started. And I can't seem to find any references to this issue in google searches.
Anyone seen this before?
I had the same problem after some time researching I found that:
You can't debug the release APK!
you can just use the debug APK
for more ref
The problem turned out to be using a css style on an Ionic Modal or Popover. Specifically, using border-radius:1px. If defined, the web UI portion of Chrome Inspector would black out. So to troubleshoot my app development using Chrome Inspector I would have to disable that css style until it was ready to deploy the final app.
However, since then...and within the last 2 weeks or so, it appears that Chrome has fixed this issue. If you use border-radius with an Ionic Modal or Popover, you can see the bottom corners have the radius applied, but the top corners are square. Seems to me Chrome's fix for the problem was to simply remove top border-radius for rendering in Chrome Inspector.
I have built hybrid app with Sencha touch 2.3 and till recent it was working fine but i recently updated the Android System Webview via Play Store (i have moto g running android 5.0.1) and now i am encountering various bugs in UI as follows :
The selectfield picker does not work correctly now. It behaves randomly. The store bound to it has data but no items are displayed in the picker when it opens. At times items do get displayed but you cannot select the items at bottom because picker always resets the selection to the item at top.
Few screens show up blank initially when rendered for the first time. As soon as user touches the screen and moves a little bit the whole screen/view becomes visible.
Also there might be other things that might have broken after updating the webview which i might not have discovered but this a big issue as far as developing for android is concerned with sencha touch. The webview updates are now pushed Over the Air and hence many things may break in future.
I also confirmed the above bugs in older versions of android wherein the webview has not been updated and the above bugs do not show up in.
I am thinking of using crosswalk as the solution to the issues with the webview. Anyone with the same issues or any tips regarding a fix ?
I ran into a similar issue with my Sencha Touch app (almost nothing rendered). Here is the workaround I used which seems to work great:
http://trevorbrindle.com/chrome-43-broke-sencha/
Thanks #Ian. The link was tremendously helpful and it solved the issue for now. Sencha has not officially released a build with these fixes so the overrides are the only solution right now.
For anyone facing same issues here is one more link from the Sencha Forums where all the issues sencha frameworks are facing with Chrome 43 are stated and solved.
https://www.sencha.com/forum/announcement.php?f=92&a=58
I am also stuck with same issue and i found solution we should not update the chrome. Better download 42.0.2311.152_chrome64_installer which is offline exe for chrome.
I'm using the ImpactJS framework for work and I've tried what most of people did to get their games to work but with no luck, most recently I tried following the instructions from this thread: http://impactjs.com/forums/help/cocoonjs/page/1.
It seems whatever I do CocoonJS refuses to launch the Impact framework (I've tried with both a game and with just the framework alone but nothing happens), whenever I launch the game I get a black screen running at about 60 fps.
Again I'm just trying to get the framework itself working but even that seems impossible. Does anyone have any suggestions?
I'm pretty sure you have a javascript error (see console log), or maybe you have debug enabled on ImpactJS (debug requires DOM, not supported by CocoonJS)