I can't find "Begin Upgrade" at Firebase > Dashboard as described at https://support.google.com/analytics/answer/10960488
Is it because I already upgraded (I can't remember that...), or my project can't be upgraded due to eligibility issues?
UPDATE:
I followed the steps provided by Matias N Goldberg (thank you!), and it appears that Google Analytics is upgraded for my two projects.
However, even though both projects are upgraded, one project shows old UI while the other shows the new UI (e.g. "Add Filter" vs. "Add Comparison")
Why is that?
Screenshots followed:
Project 1:
Project 2:
Go to Project Overview -> Project Settings -> Integration -> Google Analytics -> Manage
If you haven't upgraded yet the following should appear:
If it doesn't appear, then you already upgraded or there is a bug (this feature just rolled out so expect possible trouble)
After a successful upgrade, you should see "Linked Google Analytics account" like in this picture:
Related
I've been trying to figure this out for several hours with no luck.
In older Flutter projects within Android Studio the Firebase Assistant appears in my Menu Tool-> Firebase; however, when I start new Flutter projects Firebase Assistant does not appear in the Tool's menu. Trying to open Firebase using search, produces a search result, but launching it fails (just an endless loading screen).
I've tried all of the listed items in these previously asked questions:
Firebase assistant not showing in Android Studio 3.4.1
Unable to find Tools > Firebase in Android studio 2.2.3
Firebase assistant not showing in Studio 2.2.3
I am using Android Studio 4.2.1
I've run updates on everything that I can think of to update.
The generally accepted answer in the previously asked questions referenced above is to ensure that the three Firebase plugins are enabled. I've verified that they are:
In older projects where Firebase Assistant appears in the Tools menu, if I disable the three plugins and restart, Firebase Assistant disappears from old projects. When I then re-enable them and restart, Firebase Assistant returns to the Tools menu in older projects. However, in a freshly created Flutter project, disabling and re-enabling the plugins does not cause Firebase Assistant to appear in the tools menu.
One person suggested making sure that you are logged into your Google account. I'm logged in, but that doesn't change anything.
I don't understand why it is available in old projects, but not in new projects.
I assume I'm simply overlooking something.
Any suggestions?
Thanks
EDIT:
Since posting this question, I have tried completely uninstalling Android Studio and performing a clean install of it, Flutter and Dart. However, I have the same result. Older projects have Firebase Assistant and new projects don't.
While trying to figure out the differences between the two projects in the hope of finding something which might explain why one project does have the Firebase Assistant available and new projects do not have Firebase Assistant available, despite having all the same plugins, build.gradle information and pubspec.yaml information, I happened to notice one difference.
In my older projects, the ones that have Firebase Assistant available, if I right click on the project's lib folder and try to add a folder, instead of being able to add a "directory", it gives me the option to add a "package". Here is a screenshot of what it looks like:
However, in my new projects, the menu looks different. It says "directory" instead of "package" as shown here:
I don't know if whatever is different about my projects that is causing one to say "package" and the other to say "directory" is the reason that the project with "package" in the menu has access to Firebase Assistant, while the one with "directory" does not; however, I suspect that it might be.
I haven't been able to find anything that explains why one project would have "package" while another has "directory"; does anyone have an explanation? I would love to test out whether that difference is the reason Firebase Assistant isn't appearing.
You can try to run 'flutter clean', then re-sync the graddle.
I am assuming you are running android studio in administrator mode ? I had problems if I was not in administrator mode.
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.
Need Help !!
We are getting caution message on top of the Dashboard in Firebase Crashlytics. We are tried with different technical advises in different forums.
But nothing has worked out for us. We are still seeing the caution message at the top (in red strip) and crashes count is incrementing on every crash but doesn't come to Dashboard.
Here we go with our Firebase Crashlytics integration with project :
We are using Firebase Crashlytics with Xamarin Forms project to record any crashes in Mobile Application.
Since, Firebase Crashlytics SDK & Documentation are mostly on Native Platforms (Android & iOS). But, we still got provision to get packages from NuGet.
Here is the checklist which ensures we are on right direction:
1) Is App released with proper Apple Distribution Provision Profile and Certificate- YES
2) Is Distribution Provision Profile valid in terms expiration date - YES, it is valid till Next year from now.
3) Is GoogleService-Info.plist correctly placed. YES- it was downloaded from Crashlytics console with proper identifier configured. File was placed at root of iOS Project and set Build Action as BundleResource.
4) Did we call required initialisation function at proper place. - YES. Below set of codes ensures we initialised properly Firebase Crashlytics in AppDelegate.cs class.
5) Is your build configuration rightly placed in Release mode. YES
6) Important Point: Firebase Crashlytics was able to process the reported crashes with earlier version of iOS build which were having same project and package configuration and we could able to see the Crashes in readable format till for immediate previous versions.
But suddenly it stopped working when we promoted to production in AppStore (means LIVE in AppStore)
7) Have we uploaded to dSYM file manually to Firebase Crashlytics - YES we TRIED. We followed the steps to upload dSYM using XCode-SWIFT project with POD files.
Here is the setup and step.
POD was installed in appropriate XCode workspaces.
Run Script was executed with recommended POD commands.
Build was succeeded.
Hence, as you see, we are practiced with every advises whichever mentioned in any forum. We have applied, but we don't see, it is coming to Crashlytics Dashboard even then.
Try below command. May be help full.
msbuild "/Users/xxx/projects/myApp/myApp/myApp.iOS/myApp.iOS.csproj" /t:"build" /p:Configuration="AppStore" /p:Platform="iPhone" /p:BuildIpa=true /p:FirebaseCrashlyticsUploadSymbolsEnabled=true
I have tried this command and it is working in my case. I get it from this git thread : https://github.com/xamarin/GoogleApisForiOSComponents/issues/386
when searching the internet, i came across the TideSDK which I learnt was made for develoing desktop apps with HTML, CSS & Javascript. As an experienced web designer I downloaded it hoping to begin creating desktop apps with my HTML, CSS & Jscript experience immediately. But, that wasn't the case.
Immediately I launched it I saw just two buttons one to import, the other to create new project. Since I had nothing to import, i opt to create new project. After filling the spaces for project type(project type was fixed on desktop), name, app id, directory, company/personal URL,the Titanium SDK Version was left inactive ( I don't know why but i thought it was minor), I expected to see some spaces to write my codes but none. Rather after saving my changes, I brought to a 'console' which was also inactive. No cursor at all except some buttons with lauch app, kill app, package with Runtime, package without runtime which were all not yielding any result. Infact after clicking each of them, I still remained in the inactive console.
In my curiousity to get things working, I have done many researches on the net without a fruitful result. The best article I have gotten so far is from: http://seyekuyinu.com/how-to-set-up-the-tide-sdk-developing-desktop-applications-with-html5-css3-and-javascript/ but even that did not work fine. I downloaded the Tiv Community App which suppose to serve as the IDE but it could not be installed.The installer always stop on the way. I have tried to instal it on my home laptop and the office desktop but it could not be completed in any of them. Please if you want to reply to this question, i would love you to download the Tiv Community app and see what am talking about. I have also downloaded the helloworld from Github but when I try to import, it gives an error message something like "Importing desktop project, but not desktop SDK found in your system". I downloaded the desktopsdk-1.2.0.C4-win32 but the installer is not work - 'cannot locate application path'.
Please, am curious about this whole project and would appreciate any useful reply. I would also appreciate if TideSDK Developer team could write a comprehensive 'getting started guide' but the guide avaiable now is not meeting up with our curiousity for getting started in SDK. Thanks
Checkout Getting Started Guide http://tidesdk.multipart.net/docs/user-dev/generated/#!/guide/getting_started
TideSDK's latest release version is 1.3.1-beta
You need to download the SDK from http://tidesdk.org and extract the same in appropriate directory as mentioned in getting started guide.
I had recently upgrade our development machine to Xcode4 and after the initial interface change has gone quite smoothly.
I'm now in the process of using Ad-Hoc distribution on it for the first time so I followed this guide to set up profiles/schemes etc. http://diaryofacodemonkey.ruprect.com/2011/03/18/ad-hoc-app-distribution-with-xcode-4/
This is the process I took:
1/ Setup a new provisioning profile under distribution. I selected Ad-Hoc, the correct App and my UUIDs.
2/ Installed the profile within Xcode 4.
3/ In xcode duplicated the Release Configuration and named it Ad-Hoc.
4/ Under Code-Signing made sure Ad-Hoc had the new profile selected.
5/ Edit Archive scheme and selected 'Ad-Hoc' Build Configuration.
6/ Select Product > Archive and made sure the profile listed was correct.
7/ On save screen selected 'enterprise distribution' and entered the App URL and Title.
8/ Copied the resulting ipa archive, plist and mobileprovision (downloaded in point 1) to our http server.
9/ Added the required html to and pointed mobile Safari to it.
10/ Selected the mobileprovision which installed without a problem.
11/ Selected the App which begins to install resulting in "Unable to Download" at about 90%.
I've tried several potential solutions from other posts but they all result in the same thing. This is used to work fine in Xcode 3 (using normal developer account, NOT enterprise) and as far I can tell I'm not really doing anything different so what am I doing wrong?
Thanks.
Try this: Open the Scheme you are using to edit it. Then check if in ALL the build phases (Build, Run, Test, Profile, ...) the Build Configuration is set correctly. If not set it to the correct configuration and build it again.
If this does not work ad a new Entitlements.plist to your project and add a new value with the key get-task-allow to NO.
Edit: Have you tried to make Product > Build For > Build For Archiving and then Product > Archive.
This worked for me.
we just had the same problem (and we still have it for one device only working on iOS5 Beta, not sure if it is related. All other devices work.), some tips that could help :
Apple dev site:
your provisioning profile could need to be renewed on the apple web site.
on the apple web site check that the device is linked to the provisional profile in the "Device" section. In the "provisional profile" section, the "Edit" feature could lie to you. To add a missing device to a provisional profile, go the "provisional profile" section then uncheck and check back the missing device (the lying part from apple web site ;))
in xcode:
I switched deployment target OS from 4.0 to 4.2
I plugged my iPhone and selected it as target before to create the archive.
this issue doesn't depend on the "team provisioning file", we could build a working archive with another provisioning file too.
If it can help too, I created a doc for distributing the Moodle app but it's generic to any app I guess: http://docs.moodle.org/dev/how_to_distribute_iPhone_test_app