I have a field service reporting android app that I created in Oracle MAF. it has been in use for almost a year now with no UI issues, Over the last few days, I have been getting reports from our end users that the button text is disappearing. so - anywhere where there is a button with text inside it, the text is not visible. same font is being used elsewhere in the app with no issues. All the end users are running this on the Samsung Tab A 8.1. The last android update for the device was a few weeks ago. The problem is slowly propagating, like only 4-5 users a day are reporting that they go to use the app and the text is gone. luckily they are used to the app and know what all the buttons do, but I have to eventually fix it. I can't get any straight answers from Our IT department or Samsung as to why it is happening like this, and the update didn't seem to have anything in it that could do this. A factory reset fixes it for a day or two, and then the issue comes back.
What it is supposed to look like
Example of missing text
Like I said, this has been working fine for a while now. I'm mainly looking to see if anyone is aware of an Android update that would cause this, or if there was anything in the Samsung security update that would do it.
Google pushed an update to Chrome that they have discovered caused problems like this, and many others.
I was able to instruct my end users to disable chrome and let it roll back to the factory version.
this fixed the issue.
Related
I have recently finished developing an application and I wanted to publish it between few friends to test it.
I have sent it to 4 different users where 3 opened it without any problem while the 4th user receives the following error:
Is there any reason why it happens or how I can fix it?
Thank you
Anthony from the App Distribution team here. We have found the root cause and pushed out a fix yesterday.
It turned out that we were not handling the iw locale properly (which is an old, deprecated version of he that some devices still send). Now, we properly load the page and show Hebrew for that specific ISO 639-1 code.
Testers should now be able to use the site without issue. Sorry for the inconvenience!
I had the same issue, I finally managed to narrow down the issue to the browser type which is launched once clicking on the invite link. On Samsung devices, the default browser is "samsung interent" which couldn't handle properly(not sure why) the invite link, once setting the default browser to chrome everything worked as expected.
I've just managed to solve this issue on Galaxy Note 10.. had no problem on Galaxy S9.
Solution:
1 - Following the answer from Evgeni Roitburg I've copied the actual link from the "accept" button, using the "share" function and sending it to myself.. and opened it manually in Google Chrome, but it still gave me "404"..
2 - Out of instinct I've tried to change the phone language to English, it was in Hebrew.. After that the link started to work when opened in Chrome.
Need to mention that I've also made sure that the "user" on this phone's GooglePlay is the same gmail user which was invited via Firebase.
It seems that there is no mentions of this issue in the internet after searching Google a little.. Hope this solution will help you.
In app purchases on my app have worked fine for 2 years, and I think they are still working okay in Google Play with actual purchases. But recently when using promotion codes, or internal/beta testing, when I try restoring a purchase, I get the following error:
Error - you already own this item
If I try to purchase an item, it looks like the purchase flow works properly. But then once it is done, I get the same error above. And I can’t restore anymore.
I’ve tried all the advice out there on resetting Google Play/Services Cache, and this person several years back seemed to have a similar issue that was never solved Error You Already Own This Item. Most other discussions on this topic are fairly old and outdated.
One strange temporary fix is that if I revert my Google Play store to factory settings (I'm on a slightly older 3 year old device), it will work again... until Google Play store updates, and then it stops working.
I was using this library successfully https://github.com/anjlab/android-inapp-billing-v3, but I thought maybe since it is outdated this might be the issue. However, doing it even without this library (using official Google documentation on setting up IAB) still results in the same problem.
Does anyone know how to fix this?
Thanks!
For issues with the Google Play Billing Library I would suggest filing a bug on the public issue tracker listed at https://developer.android.com/google/play/billing/contact.
I'm trying to make a really simple app for a friend to display his bar's ordering website in an app for when they reopen with the social distancing measures in place. The web app already exists, so this is really a simple matter of displaying the content in a WebView.
I've got the page loading, the content is visible, the styling is done - The only problem is that it doesn't seem to be loading all the elements. There's a line of filters at the top which just display as 3 dots (i.e. loading), and when I click any of the items on the menu, nothing happens. There should be a window pops up asking for a table number etc... If I open this in the Chrome browser on my phone, rather than a webview in the app it works perfectly so I know it isn't the website.
I've done the following;
setJavaScriptEnabled(true);
setJavaScriptCanOpenWindowsAutomatically(true);
setSupportMultipleWindows(true);
I've also turned off safe browsing in the manifest in case that was blocking anything. I have also given the app permissions to use the internet. I can't figure this one out at all and nothing online seems to be helping!
Admittedly I'm a tester (automated, but still), so coding isn't my best suit. I may be missing something really simple here. Any ideas?
Scratch that. For anyone who's interested, I needed to add this line;
setDomStorageEnabled(true);
For such a simple thing it proved impossible to find info on, I just enabled everything until something worked! So hopefully you don't have to do the same if you're looking at this.
This is a weird question, because the error "java.lang.RuntimeException: Waited too long for browser bridge" is annoying me only since yesterday, while before everything was working like a charm. It is weird because I haven't changed anything to the app (before it is working, and in a moment is not working anymore)!
This is the error:
I attach the image of the situation in cgt.java:135 if i put a breakpoint in the specific line .
It is weird also because now EVERY apps I have deployed with a MapConteiner and Googlemaps API is giving me the same problem (and they were working well, before).
I have read the forum in CodeNameOne Google Maps, and I have already added the build hints:
Thanks in advance for any answer,
Luca
I think it's a regression in the current map JavaScript HTML fallback that tries to wait for the browser component on a map that wasn't loaded yet. You should file an issue on that.
As a workaround just invoke zoom after showing the parent form.
I use a Material Spinner in a fragment and I want to request focus for it programmatically. The weird thing is, that it already worked several days ago. I checked my old version, where it is also not working any more. So maybe it is some Android update issue. The library was not changed in the meantime.
For requesting the focus i use these lines of code
inputHardness.setFocusable(true);
inputHardness.setFocusableInTouchMode( true );
inputHardness.requestFocus();
Please help me, I am quite stuck.