I wrote the androidx follower in the Android Studio, but I could not find it. How can I add it knowing that the version is old 2.2.1
Related
We have created our Teams FX project using Teams Toolkit v 3.7.0 and we have already released our app to the production.
TeamsFX CLI version from package.json: "#microsoft/teamsfx-cli": "^0.14.0",
TeamsFX API version from package-lock.json: "#microsoft/teamsfx-api": {"version": "0.18.0",
Now, we would like to upgrade the project to latest version. I have gone through wiki articles but it's not very clear. Can you please let us know the upgrade procedure. Is updating the Teams toolkit version to latest version enough or any other additional steps required.
Please let us know.
Thanks.
Latest VSCode teams toolkit extension or teamsfx cli already support migration.
If you're using VSCode, you can open the project, then you will see the dialog as below, click upgrade, it will automatically upadte your project to latest version:
If you're using TeamsFx CLI, you can run preview or provision command in the project, then it will ask you to upgrade app:
Tip: due to there is a bug for upgrade in recent version, recommend using latest version 4.0.5 to avoid migration issue.
I needed to rebuild my fairly ancient Xamarin Forms app from scratch and in the process arrived at a situation where I had a new working iOS app but had needed to delete the draft Android app and start it again. So as a next step I added a vanilla Android app project out of the box and immediately what I saw was that (in MainActivity) Android.Support, Android.Views and Android.Content were undefined with wiggy red lines beneath -- for example in a reference to Android.Support.V7.Widget.Toolbar.
Trying to solve the problem, I set each of Target Framework, Minimum Android Version and Target Android Version to Android 9.0 Pie (API Level 28). In SDK Manager I checked that Android SDK Location and Java SDK Location were 'Found' and that Android SDK Platform 28 was installed.
The following NuGets came installed along with the project, I deleted them and reinstalled them (removing bin/obj folders in between): Xamarin.Android.Support.Core.Utils, Xamarin.Android.Support.CustomTabs and Xamarin.Android.Support.Design.
I tried installing NuGets Xamarin.Android.Support.v7.*. And I added the Xamarin.Forms NuGet. I tried adding 'use' declarations.
None of this helped.
For comparison I separately installed a blank Android app solution-- it worked perfectly out of the box.
Android is pretty new to me - would be grateful for suggestions on fixing this.
The app has a .NET Standard 2.0 project, an iOS project, the (vanilla) Android project (all three with Xamarin Forms), and a .NET Standard 2.0 library project.
I'm using Visual Studio for Mac V8.5.4 (stable) on MacOS 10.15.3.
I noticed that the content of MainActivity.cs is quite different, depending whether the Android project is created separately or as part of a Xamarin Forms solution. Also the provided NuGets are different. So perhaps what I was trying to do, adding an Android app to an existing XF solution, is simply not allowed.
To fix the problem, I created an empty Xamarin Forms solution with Android and iOS projects, added a further empty library project, then in Finder replaced the content of all the project folders, except the Android one, with the content of the corresponding folders in my working solution (the one with a working iOS app).
Migrating to AndroidX is a good idea though.
I don't know if this will help, but you should migrate to AndroidX as soon as possible, nevertheless. Xamarin has migrated to them, starting from Forms 4.5
Here is some more information about the libraries - Introducing AndroidX for Xamarin
There is a special NuGet package for the migration - Xamarin.AndroidX.Migration. Also available is a built-in functionality in Visual Studio - here
What I can suggest is you try to migrate to AndroidX libraries, since the old support libraries won't be supported from now on, and you will surely encounter some issues if not like this one, then something else will pop-up in the future.
We have a Xamarin.Forms project that was created a couple of years ago and after upgrading to the latest build of Visual Studio 2019 (16.2) we are getting nearly 100 errors like the following when building the android version of the project: error: package com.google.android.gms.common.api.GoogleApiClient does not exist
I checked with a colleague who was using Visual Studio build 16.1.3 and the android project built fine but after upgrading their Visual Studio 2019 to the 16.2 build they now get the same problem too. The iOS project continues to build fine.
Does anyone have any suggestions on what to try? I found a bunch of older posts that suggested adding items in the Android SDK manager but none of these changes helped me.
Failing that does anyone know of a way for me to revert my Visual Studio install back to 16.1.3?
Have you updated all NuGet packages? Did it help to move to VS 16.3.5? Have you checked the dependencies of your NuGet packages?
I am having issues with an activity being placed outside of application. It seems like the Google Ads/Admob implementation in Xamarin apps is a source of troubles. Net Core version also seems like a good place to check for a solution.
I am trying to install Microsoft.AspNetCore.SignalR.Client on Xamarin forms (on .net standard 2.0) and run the android app. I keep getting the error
Could not load assembly 'System.Threading.Tasks.Extensions' during startup registration
I have tried installing System.Threading.Tasks.Extensions nuget's latest prerelease, I still get the same error. I did not find any one else with this issue online.
You need Visual Studio 2017 Update 15.8 + Microsoft.AspNetCore.SignalR.Client Package with at least Version 1.0.1
ASP.NET Core 2.1.1 contains fixes to resolve blocking issues when
using the SignalR Client from Xamarin. However, these fixes also
require an updated build of Xamarin.iOS and Xamarin.Android, as
well as some additional dependencies.
In order to use the SignalR Client in Xamarin applications you will
need to:
Upgrade Microsoft.AspNetCore.SignalR.Client to 1.0.1.
Upgrade Xamarin to the appropriate version:
Xamarin.Android 8.4.0.1
VS2017 Update 15.8 comes with Xamarin.Android 9.0.x tools which contains the fix for the issue.
Trying this : https://learn.microsoft.com/en-us/azure/app-service-mobile/app-service-mobile-xamarin-forms-get-started-push, using VS 2017 portable Xamarin Forms project. Except UWP all other projects including IOS , Android and Portable library are getting installed with the Notificaiton nuget package. In UWP its always failing with the below error message. Thanks for your help.
Package Microsoft.Azure.NotificationHubs 1.0.9 is not compatible with uap10.0.10240 (UAP,Version=v10.0.10240) / win10-x86-aot. Package Microsoft.Azure.NotificationHubs 1.0.9 supports: net45 (.NETFramework,Version=v4.5)
As of July 2016 Notification Hubs SDK is not available for UWP. The product team is aware of it and working on providing it.
At the moment, there are one way to workaround it:
Use WindowsAzure.Messaging.Managed Nuget package as described in Getting started with Notification Hubs for Windows Universal Platform Apps
Certain Hubs SDKs are open sourced. But, unfortunately, not Windows ones at the moment.