In my app, I am trying to use Firebase crash10.2.1, but I cannot get gradle to compile. I keep getting the message :
'Failed to resolve:com.google.firebase:firebasse'
I faced the same issue when I tried to use firebase-messaging:10.2.0 and to fix that I did this:
On Android studio, go to the menu bar and click on Tools > Android > SDK Manager.
Click on the SDK Tools tab
check the Google Play services box as well as the Google Repository box.
Click on apply, it will prompt you before applying the new updates.
Click Ok and wait for the download
Sync your project again and everything is fine.
also check for correct version
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'm reporting a very strange problem.
I have an app developed in Flutter and I have correctly integrated the Firebase library for using the Dynamic Links service.
The problem is when short links are open on a mobile device, it shows a screen with the message "Save my place in the app. A link will be copied to continue to this page", and a button OPEN to continue.
Using your link debugging tool everything seems ok
When I develop directly in debugging mode the problem does not present itself.
When I install the app from TestFlight sometimes it works and sometimes it doesn't. It seems random.
the problem could be that the app is not yet available on the store ?
With the new Google Play console update, I can't seem to find the option to download an APK for a release. Has this been removed? I have tried to look over sub-menus but no success.
Not sure if this functionality has been introduced with the updated Play Console, but now I am able to download the APK:
App bundle explorer -> Downloads Tab
And at the bottom, you should have the original file.
I am using Xcode 8 and trying to upload my watchKit app to Testflight but its failing all the time.so far i have tried these options,
tried uploading it from Application Loader 3.6 and get invalid swift support, invalid watchkit support,and invalid executable error.
tried from Xcode 8. The app validates succesfully but upon upload to store, it just gets stuck. when i refresh, i do get an upload sccessful message but nothing is visible on testflight.
how to upload my watch app on testflight? please help
Have you enabled the version of your app to test on the iTunes Connect website?
I hope I'm not stating the obvious here, but if you:
Select your app in the "My Apps" section
Select the "TestFlight" tab at the top
Select "Internal Testing" on the left hand menu
Click on the "Select version to test" link in the page
Uploading an archive with a new version number doesn't automatically add it to TestFlight, so you have to go through this procedure every time you change version number (or on the first upload).
Once it's added, you should see the app appear in the TestFlight app on your phone. When it also has a Apple Watch app, and you have a watch paired with your phone, TestFlight will also install the app to your watch.
Hope that helps!
when using xcode 8 doing the push notification setting, unlike xcode 7, xcode 8 need developer turn on push notifications capabilities switch ( located at TARGETS -> AppName -> Capabilities as following pic ),
then it will generate AppName.entitlements file as following
//AppName.entitlements
<key>aps-environment</key>
<string>development</string>
but for production version App, if we change the string to
//AppName.entitlements
<key>aps-environment</key>
<string>production</string>
then the Capabilities show a warning
and it seems no matter which string value specified in aps-environment, we can still get the push device token at application:didRegisterForRemoteNotificationsWithDeviceToken:
so what is the correct setting of the push notification entitlements?
thank you
I was struggling with that today in Xcode 8 GM. After disabling the setting, deleting my developer portal provisioning profile and regenerating it and enabling the setting again, I was able to eliminate the warning in Xcode. Keep in mind that I didn't fiddle with the entitlements file. I left it at development environment and after archiving I got the correct aps-environment setting (production).
Seems Xcode is stilly very buggy tho even in GM
My problem was my pusher client was out of date and would only push successfully to debug tokens. Other issue which I am still working on a fix for is that I could only export the app via gym with legacy-api enabled, this was not setting the apns-environment to be 'production' and leaving it as 'development' in the 'embedded-mobile.provision' file. I have however been able to successfully deploy the app via the xcode organiser to work with apns(prod) now.
I think the better solution is open the project package and open project.pbxproj
change the CODE_SIGN_ENTITLEMENTS
CODE_SIGN_ENTITLEMENTS = "your-app/production.entitlements";