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.
Related
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.
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 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.
I'm testing on an HTC Sensation, running android 4.0.3.
I'm publishing using FlashDevelop 4.0.3 and using the Air Mobile AS3 App template.
All the application does is display a Rectangle using:
this.graphics.beginFill(0x00FF00);
this.graphics.drawRect(0, 0, 100, 100);
Just so I can see that its actually publishing something.
The app runs correctly if I publish to the desktop, however when I switch to publishing it to the phone, the problem I'm facing is that the application publishes and runs on the phone, but only for a few seconds.. usually about 4 seconds and then it crashes out.
The really weird thing is that it was working fine about a week ago.. I'm not sure what's changed since then, but yeah it started happening this morning, I tried everything I could think of... including stripping everything out of the app and also doing a factory reset of my phone... nothing seems to have helped...
has anyone else had this problem? or have any ideas on what might be causing it or how to fix it? any help would be greatly appreciated.
Cheers
Update:
it seems changing the render mode to "auto" instead of "direct" stops the crashing, which is great, however if you need to use direct for stage3d content this doesn't really help. anyone else having this issue?
Can you post the source code of your application? I do too have HTC Sensation but my firmware version is 2.3.6. It would be interesting to test it.
I just updated my XPERIA ARC to ICS and now I'm having problems with AIR apps as well. Seems the app is not getting the Click/Touch interactions. Some InteractiveObjects like TextInput gets the click and focus as it should, but Buttons are not working. And I'm using latest Flex/AIR sdks...
But I'm pretty sure we are in Adobe/Apache hands until they update the AIR with a fix.
As the titles state, I can't drag widgets onto the screen. Attempting to do so simply produces a dashed outline, but the widget isn't added. Different widgets cause differently-sized outlines to be created, so the application (Eclipse) is recognizing my input to some degree. No errors are produced either.
I've found no documentation on the drag-and-drop UI approach, probably because it's supposed to be self-explanatory (I had no problems doing the same thing on Qt, for example). Also note that I've gotten a basic "hello world" program working, both on an emulated device and on a smartphone.
I tried uploading a picture illustrating the problem but as I am a new user I don't have the permissions to do so.
EDIT: Well restarting Eclipse fixed the issue, though I still don't know what caused it.
Well restarting Eclipse fixed the issue, though I still don't know what caused it.