Firebase test lab results - missing performance data - android

I've just uploaded my apk to Firebase and run a "Robo" test.
Test passed, I can see screenshots, logs and video, but there is no performance results. It says "There is no data at this location". Also in the video tab, there are no graphs underneath.
This is how it should look like according to the Firebase docs:
https://firebase.google.com/docs/test-lab/images/performance-results.png
Any ideas what could went wrong?
I've run this scenario on Pixel, API Level 26. My app is an OpenGL game.

Sometimes the performance tab does not load initially. With the performance tab showing, simply reload the whole page and see if it shows up. I ran into the same issue and reloading fixed it for me.

Related

Flutter: Importing image Url from Network error

Hello I am new to flutter and was doing an ecommerce app while importing images URLs from firebase SOMETIMES while calling the "Image.network" gives me this error but only sometimes, and with different picture URLs(every time it is random and sometimes it loads every picture)
which is weird I don't know how to solve it .
Here is the exception it gives.
Here is mobile emulator picture
as U can see it's different every time.
There appears to be a few solutions that people have come up with. On the Flutter GitHub issues page this "hack" appears to have helped some people:
Potential Solution

Cannot complete "Ads" Section

In the area of "Let us know whether your app contains ads" in App Content, this section tells me that I have to complete the next section
You must let us know whether your app contains ads. The 'Contains ads' label is shown next to apps with ads on Google Play. Make sure this information is accurate, and is kept up to date.
here
But when I go to the option, it just show me
this
For me, it was the Ad Blocker. I disabled my adblocker and refreshed the page and it worked.
#Mate Farkas's answer (worked on phone) inspired me to test this.
Try to complete the section on your phone.
I'm chasing the same issue for an hour now. On Chrome+MacOS I'm seeing the same error as you, on Chrome+Android (Pixel 2) it works for me.
I ended up downloading Chrome to see if the problem was the browser (I was using Edge Chromium), and the option appear, seems like is a bug with Edge Chromium.

Xamarin Android app built using MvvmCross stuck on splash screen when resumed from background after 3-4 days

I am working on one Xamarin Android project which is using MvvmCross version 3.5.1. I am facing one issue which we thought might be because of MvvmCross set up failure. App is basically for both platforms Android and iOS. But, i am facing an issue specifically for Android. App is quite old and in development from last 3-4 years and never upgraded to latest released versions of MvvmCross. Updating MvvmCross is last option for me. But before that I want to fix this issue by knowing it's root cause and way to reproduce it.
Scenario:
1) App installed on Android device, Login is done.
2) App moved to background.
3) After 3-4 days, app resumed by clicking on app launcher
icon and stuck on splash screen.
4) App started working again when
force stop from phone setting
I am unable to reproduce this issue without putting it in the background for more than 3-4 days. Can you please suggest a few approaches to know the root cause and steps to reproduce this issue without putting the app in background for more than 4 days.
Below Logs printed from MvvmCross and app freezes on the splash screen. log statement in bold "No view model type finder available - assuming we are looking for a splash screen - returning null" is printed 3-4 times and then app stuck on splash screen. Even though app stuck on splash screen. push notifications are received by an application.
Setup: PlatformServices start"
Setup: MvvmCross settings start"
Setup: Singleton Cache start"
"mvx": "No view model type finder available - assuming we are looking for a splash screen - returning null"
"mvx": "No view model type finder available - assuming we are looking for a splash screen - returning null"
"mvx": "No view model type finder available - assuming we are looking for a splash screen - returning null"
Please help me to know why the above log statement in bold is getting printed for 3-4 times and why logs from _setup.InitializeSecondary() are not printed, and then app stucks on splash. Looks like setup hung in between because of some deadlock or race condition. It will really help me if you have any suggestions to know possibilities to know the root cause and a way to reproduce this issue. Thanks in advance.
Updated:
We are able to reproduced this scenario by commenting InitializeSecondary() call from MvxAndroidSetupSingleton->InitializeFromSplashScreen() and app stuck on Splash screen. please suggest fixing this splash screen stuck from app level code. Basically, we don't want to modify MvvmCross code and wanted to fix from app code. Your help is appreciated. As per logs, a line of code _setup.InitializeSecondary(); in below method from MvxAndroidSetupSingleton.cs is not executed. This issue is getting reproduced only after keeping the application in the background for more than 4-5 days. First i am trying to know why this is happening in this particular case and then solution for it. Thanks in advance
Note: I am using Android Foreground service in my application
public virtual void InitializeFromSplashScreen(IMvxAndroidSplashScreenActivity splashScreen)
{
lock (LockObject)
{
_currentSplashScreen = splashScreen;
if (_initializationStarted)
{
if (_initialized)
{
_currentSplashScreen.InitializationComplete();
return;
}
return;
}
_initializationStarted = true;
}
_setup.InitializePrimary();
ThreadPool.QueueUserWorkItem(ignored =>
{
_setup.InitializeSecondary();
lock (LockObject)
{
_initialized = true;
if (_currentSplashScreen != null)
_currentSplashScreen.InitializationComplete();
}
});
}
We have made a lot of improvements to app startup in MvvmCross. So chances are that your issue has been solved in a newer version.
Although, since it is saying "No view model type filder available", it will probably mean that the startup procedure hasn't finished or is stuck doing something and cannot find the next ViewModel it wants to continue to.
Android will memory clear an app if it is long in the background and or unused. This means that the mvvm framework loses all of its references in memory as the same for your IOC Container. Normally an mvvm framework should be able to handle this but in my experience sometimes you have to manually give it a push.

Google Play A/B store listing testing and APK

I have an Android app and I'm doing some A/B test experiments to see how the store listing text performs.
In one of my test I changed the logo image. The problem is that I have the same logo image inside my app, as a resource file. It is shown on the splash screen during loading.
Both A and B test are serving the same APK of course so it may be confusing for users on B to see a given logo on the store listing and then a different one on the actual app.
How can I solve this? I suspect the only option available is to remove the logo image from the APK.
This is an interesting problem without a definitely correct answer. There are at least two points of view.
The first point of view says "it doesn't matter". A/B store listing experiments are about seeing which store listing works best to convert a user from "someone who is looking at your listing" to "someone who installs your app". By the time you have got to the splash screen the experiment has done it's job. Yes it is a slightly strange experience for some users, but that's ok. Run the experiment for long enough to get a result about which works best, then change both the store listing and the app to use that icon.
The second point of view says the inconsistency matters. Having an inconsistent icon will make the user confused, lead to higher tech support costs, and more uninstalls. It would be nice to make the icon match, but the trouble is, for any given user you don't know which experiment branch they were in, and Google don't give you any way to find this out. So while it would be nice to have it match you can't. This leaves you with two options:
take the logo out of the splash screen
switch to a third logo on the splash screen that is different to both experiment conditions
Personally I think I take the first point of view. But if you take the second, there are at least two things you can do.

User complaining of Android app 'disappearing' following an update

A user of one of my Android apps has reported that his version 'disappeared' following an update. None of the other (thousands of) users have reported issues.
This morning I tried to open up the app but could not get anything.
I tried and tried and then physically turned my phone off and back on.
Now the icon has disappeared.
He has a lot of data stored in the app, so removing and re-installing isn't an option.
I think the problem has been caused by another apps update which happened yesterday.
I can see your icon in my apps list but it is the only one that is black and white, all the rest are in colour.
When I view the properties of your app it says:
Storage 20.00KB
Application 0.00KB
Data 20.00KB
It gives an option to clear data or uninstall.
My memory card, which I haven't removed, says I have 55mb of data left.
What could have caused this, is there anything I can do to avoid this happening to users in the future and is there anything I can suggest to remedy his problem?

Categories

Resources