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.
Related
I've got a problem with Unity installed on Mac OS (Unity 2020.1.16f1 Personal and Mac OS Catalina 10.15.6)
It's look like Unity delete files by itself from my asset folder.
It occurs with both a Firebase (Firebase SDK 7.0.2) and PNG file.
The deletion seems to occur something like each hour (more or less)
However the problem don't happen with all my assets, for exemple with the Firebase SDK it seems that only the file FirebaseCppApp-7_0_2.bundle (and with my png file it happens only with a specific file).
Here's how I get the problem (exemple with Firebase SDK):
I import Firebase SDK I need into Unity (Import Package -> Custom Package and then choose the one I need)
Got this error: "DllNotFoundException: FirebaseCppApp-7_0_2"
Correct this error by going to Security And Confidentiality of my Mac and authorize Firebase to be open (when you download something from internet directly sometimes your Mac ask for this authorization because he don't recognize the developer)
Work perfectly for approximately 1 hour (I can make all changes I want, test my game with the game mode etc ...)
After 1 hour get the error of 2) again (on game mode)
I can fix the problem by reimport only one file from the SDK (FirebaseCppApp-7_0_2.bundle locate in Assets/Firebase/Plugins/x86_64/)
The first time I click play in Game Mode Unity crashes
Go to 3) step and continue
Is someone already get this error ? I've found multiple thread on internet talking about similar bugs (but not exactly the same) but nothing worked for me ...
I found and correct the problem. In fact the problem came from the iCloud which seems to not works correctly with Unity. For some obscur reason, the files which were deleted didn't sync with iCloud, and so when iCloud sent back the project the files were missing. You need to disable automatic sync with iCloud.
Some earlier versions of the Firebase SDK offered to add packages to the Unity Package Manager and would migrate files automatically. I would suggest using only unitypackage integration and trying to undo this migration in the process now. To see if this is the issue, do the following:
close Unity
open Packages/manifest.json and delete the entry for "ScopedRegistries" and remove any lines under "dependencies": { that start with "com.google. Note that Packages is a sibling of Assets (that is, it's next to rather than inside).
for safety, remove any Firebase packages under Assets. This include the folders:
Assets/ExternalDependencyManager, the (old) Assets/PlayServicesResolver, Assets/Firebase, Assets/Parse, Assets/Editor Default Resources/Firebase, Assets/Plugins/Android/Firebase, and Assets/Plugins/iOS/Firebase.
Download the latest Firebase Unity SDK (you can check the release notes here).
open Unity again and add each UnityPackage you need from the SDK. You can usually follow the errors in the console output if you've forgotten everything you're using.
A less likely issue you might be running into is MacOS's stricter behaviour with respect to gate keeper. There's a video here with a workaround, but since you mention the PNG files disappearing I expect that it's the External Dependency Manager.
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
I just finished developing IOS app using xcode. I want to upload it to Cydia Repo. However I searched around and it seems like they are all outdated!.
I found this deb maker https://www.b4x.com/android/forum/threads/publishing-your-apps-in-cydia-store-deb-package.61937/
But it doesn’t include the steps how to “fake sign with idid or theos, according to bigboss its a mandatory for Apps.
Is there any new tutorial or documentation? Let me know thanks
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.
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.