i just suddenly facing anomaly on my Firebase Dashboard after releasing new build version
Signed in Status where i usually filtering active user based on user_id is suddenly missing from the dashboard
this is the screenshot of my Firebase Project - Production (after new release)
it suppose to be like this :
this is screenshot of my Firebase project - development. (both before and after new release, nothing changed)
the other problem is coming when i look at the number of MAU/WAU/DAU, it was increased significantly within only one day.
active user still in 4.0 Mio
screenshot before release new version
next day after release, active user jump into 5.8 mio
screenshot after release new version
have someone ever faced similar issue and escaping out from this ? please help if you have any solution to fix this issue. this number is invalid and should be reported to management in weekly basis.
thanks for your attention :)
Related
We are using Firebase auth on a React Native app using react-native-firebase for several years now (currently at 12.9.3). A few days ago, without a new Android release or changes in the Firebase console, an Android user could login in the morning but then could not any longer in the afternoon and then after and getting this "firebase_auth/missing-client-identifier" error message.
I have searched here and at the react-native-firebase issues at GitHub but could not find any cases that this happens to only one user. Then yesterday, a second user started facing the same problem which is worrisome.
I checked the SHA-1 and SHA-256 fingerprints and everything is setup correctly and that is why thousands of other users are not facing an issue.
Any ideas of what could be causing this?
Thanks!
I am using InAppBilling plugin in a Xamarin.Forms solution.
IAP works in iOS and the app is approved and ready to release.
HOWEVER, I'm having issues getting this to work with the Google PlayStore.
The PlayStore returns the message: [productSKU] does not exist.
But that subscription item is clearly in the PlayStore AND activated with the exact SKU I'm using.
Does anyone know why a subscription item cannot be found or reached?
And yes, I've double checked and triple checked that the right SKU was being passed in in this:
var purchase = await billing.PurchaseAsync(**productId**, ItemType.Subscription, verify);
Is there any other obscure setting in the PlayStore that would cause this item to not be found?
After digging through docs and getting this working, here are some tips for those who could do with some help.
Upload your signed .apk or app bundle to the PlayStore in Closed Testing.
Submit for review. May take a few days (3 days for mine).
Promote the approved app to the Alpha track and you probably have [yourapp] Track1 too.
Setup you IAPs and activate.
Set you app as "Published" in Advanced Settings. This will trigger a review but it should be quick if the app has already been reviewed.
You CANNOT test AIPs from debug mode. You need to build in release and sign, then deploy to testing device THEN try purchase your item(s).
If I figure out how to step through in debug mode, I'll see if I can add to this later.
I've been at this for past 2 days and I'm getting weird errors from the store.
I'm trying to upload an update to my application "CoManga" via the store and it's not working out.
I'm working on Xamarin.Forms (UWP) and before making the appxbundle, I made sure and "associated my app with CoManga" from my developer account. All the information over there matches and should work fine without any issues.
Then I made a release of my UWP app, got the bundle and I tried to upload it to UWP.
It said that the Publisher info is different, so it couldn't upload. This is weird because I tried signing the bundle with my developer account itself.
Now, I tried building and signing the app bundle from app center. I got the appxbundle and that I tried to upload. But, since today it's giving me weird error :
The package comic_dl.UWP_2.1.15.0_ARM_x86_x64.appxbundle is taking a
long time to process. If this isn’t completed soon, try refreshing the
page, or remove the package and then upload it again. If you continue
to see this issue, contact support.
This package I tried to build from my system manually : https://drive.google.com/open?id=1VVvF6IB70R2DKNUgBJcqw-HryL1LIwgo
This is what I got from App center : https://drive.google.com/open?id=1o0sGKU2AKVgrcTelIoRFz7QCe8Do0WJ3
This is the Store ID : 9N81F8B5WW93
Can someone guide me what I might be doing wrong/missing something.
Thanks
EDIT Update : So, I followed the suggestion and contacted Microsoft's Team for help on this issue. After 3 months of multiple contacts, I was able to get someone to reply back and follow the case. Even they tried things on their end and I tried by deleting all the certificate files I had in my current project and tried to manually build the manifest file and then it worked. I'm not entirely sure what worked out in the end. But, you can try these things if you run into this issue.
1.) Clean your project.
2.) Delete .vs directory.
3.) Look for any certificate files in your project. Back them up somewhere else and then delete them from the project (Don't exclude from project, just delete them entirely). Clean and rebuild your solution.
4.) Check if the application is already installed on your system (When you debug, VS will install your UWP app on your machine to run it). If it's installed, uninstall it completely.
5.) Make a backup of your manifest file and try to create a new manifest file.
These are the links I received from Microsoft Help:
PFN and package publisher name must match values here: https://partner.microsoft.com/en-us/dashboard/products/{YourAppID}/identity
Update manually: https://learn.microsoft.com/en-us/uwp/schemas/appxpackage/how-to-create-a-package-manifest-manually
Update in VS: https://learn.microsoft.com/en-us/uwp/schemas/appxpackage/uapmanifestschema/generate-package-manifest
If these values were pulled from test certificate, partner needs to update their test cert: https://learn.microsoft.com/en-us/windows/msix/package/create-certificate-package-signing
I think this problem is not caused by anything code related, but rather it is a problem on the Store side. I would suggest contacting the Store support, they should be able to investigate if there is something wrong with your app package or the problem is on their side.
For support go to the official website, click the Contact Us tab and fill out the form accordingly.
The team should be able to advise even for the first error with different publisher info. If your app was always associated with the same account, there is no reason it should give you such an error message.
I had this issue gazillion of times. It is so frustrating. That error message isn't useful at all.
Anyway - I think it is something in Package.appxmanifest, something in Identity tag.
Retrieving some necessary info from store helped me.
Click right on your project -> Publish -> Associate App with the Store. This will update Package Display Name,Package Name,Publisher ID,Publisher Display Name and Version with correct values (within Package.appxmanifes).
Also be careful with version number. The last from numbers must be zero. 1.1.1.0 is fine, while 1.1.1.1 is not.
We are setting up a new version of our app and we are switching from the legacy (v4) GTM SDKs to using the v5 mobile Google Tag Manager via Firebase.
On Thursday and Friday morning I ran some extensive tests on our tracking setup on Android and found a number of bugs in the GTM setup. I fixed them and then republished the app around mid-day on Friday.
On Monday morning (yesterday) I ran some additional tests and none of the fixes that I made worked, in the sense that the data that reached Google Analytics (the ultimate endpoint) showed the same errors from the previous round of testing.
My only conclusion is that the container didn't automatically update over the weekend (according to this, it should update every twelve hours).
I am pretty certain that this is the problem because some of the fixes included updating lookup table variables (we don't pass event category / event action as parameters from the app, these are mapped via two separate lookup tables), and the event category / action values were unchanged in GA in the second round of testing, even though they had been altered in GTM in between.
The documentation is a bit vague on exactly how the update process works - is there a way to debug exactly how to set up GTM in the app to ensure that it will automatically update when the container is republished in the GTM UI?
OK, the answer was pretty simple in the end, but as far as I can tell this is written nowhere in the documentation.
So, all you have to do is not rename the JSON file that you download from the GTM web interface - that's it! Our Android devs had renamed the different versions as gtm_dev.json, gtm_test.json, gtm_prod.json, etc, and this caused the automatic update to fail. That's it!
So if you are googling this error, double-check that your JSON file in the app has not been renamed.
In trying to add an app group (for an apple watch app that can share data beween the phone and watch) I always run into this problem, where the first step ("add the app groups entitlement to your entitlements file") gets checked, but the other 2 steps have red errors because of this "unable to create a provisioning profile because your team has no devices registered in the member center" problem.
I've downloaded test projects where people show how to share data between the phone and watch, but they never work for me in the simulator (always gives nil data) whereas they do for other people - I believe it's because of this app group error I'm getting where only 1 of the 3 steps is ok. I don't have an iphone so I can't register one in the member center as it wants me to. And going to Build Settings -> Code Signing and manually selecting a provisioning profile (as is necessary when submitting iphone apps when you don't have an iphone, as I've done before) still doesn't solve these app group errors.
Has anyone without an iphone got an app group working properly with all 3 steps? Would appreciate any help.
Read carefully this tutorial: http://weblog.invasivecode.com/post/108082269360/sharing-data-between-apps-and-their-extenstions
As far as I can tell (after trying to get around it for a few hours) you definitely need an iphone registered in your developer profile in order to use app groups in the current xcode watchkit beta. Someone correct me if I'm wrong.