In following the steps to set up Xamarin Hot Restart (below), I could not get the "Download All Profiles" button to work.
https://learn.microsoft.com/en-us/xamarin/xamarin-forms/deploy-test/hot-restart
Operation just never completes. I likely don't have the correct permissions from our Apple Store admins. What permissions should I ask for to all this step to work? Or is there something else to try? I was able to manually download our main provisioning profile, but I don't know where to put it on a PC.
I also tried manually selecting the provisioning profile in the iOS project's properties. The only one I have has an odd name: "Unknown (Name of Our Main Provisioning Profile)". I went through the set up for my iPad and after seeing it in the deployment target drop-down, tried to deploy and debug on the iPad. The error I get is "No iOS signing identities match the specified provisioning profile 'Name of Our Main Provisioning Profile'". Any ideas?
I was able to manually download our main provisioning profile, but I don't know where to put it on a PC.
You need to install certificate and provisioning profile on mac first , and then enter your Apple Developer account credentials in vs for windows (Tools-Options-Xamarin- Apple Accounts ) ,at last select a development team using the dropdown menu in order to enable automatic provisioning in the project.
Ref : https://learn.microsoft.com/en-us/xamarin/xamarin-forms/deploy-test/hot-restart#initial-setup
Related
So I am trying to run apps on my phone. I do have Xcode 13 and running iOS 15. Not sure how relevant that is.
So when I run the app I get the following errors:
Xcode:
The operation couldn’t be completed. Unable to launch app because it has an invalid code signature, inadequate entitlements or its profile has not been explicitly trusted by the user.
iPhone:
Your device management settings do not allow using apps from developer "Apple Developer: Name" on this iPhone. You can allow using these apps in Settings.
So I have gone to Settings -> General -> VPN & Device Management to allow the app but nothing pops up. I have also tried signing in an out of the account on the Mac. I have even uninstalled Xcode and reset the computer. I am not sure what else to do.
I can tell you that my paid developer account has expired. Not sure where to go from here.
I thought it was because my membership expired. However, even after paying and renewing my membership I ran into the same problem. Eventually I was able to fix by:
remove my account from xcode
delete developer certificates from my keychain
add the account again
When I tried to run the app on my phone, I got the same error message. However, this time my developer account appeared in settings > general > VPN & Device Management, and I was able to allow it.
Tried the new Apple ID but Xcode does not allow this with the new developer account as I was unable to generate provisional certificates. Per Apple, this is only for paid subscribers.
It seems from iOS 15 onwards, it is not possible to run apps physically on the iPhone unless you pay the annual subscription. That’s a shame!
From what i understand, this might be a bug connected to iOS 15 / xcode 13.
I found a solution which is to create a new Apple ID and use it to sign your app in xcode.
You can add a new team by going into "Signing & Capabilities"-tab and select "Add account" where you select a team. It does not have to be a paid developer account.
Once you've done this and run the application on your device again, the option to trust the application in Settings > General > Device Management should appear!
I've had this a while, the paid membership expired. Upon renewal, I was continuing to have this error. Turns out my error was that I did not have the "Push Notification" entitlement added to the project - removed it when account went free.
To test if you need to enable any entitlements, you can archive the project and upload to TestFlight. The email confirmation later received will tell you if there are any and which entitlements are missing.
I am trying to publish a project from Visual Studio 2019 (fully updated) to azure. But when I try to login I get the message:
Your account is at risk
To help you—and only you—get back into . I verify my account by sms message and enter the old and new email address. But then again when I try to login it again wants me to verify.
At the same time, the email works when I go into Azure portal and I also managed to deply a Microsoft SQL database into Azure SQL. (Though initially I had to add the IP address in the firewall on Azure). Also I updated the location of the user to Thailand (Where I am), in case the system matches the IP address to the location.
OTher things I have in place are for example the resource group. And I also tried to create an app in Azure portal and then publish it to this, but the issue is that I can't login from Visual Studio.
Any suggestions on how I can publish a project to Azure?
------- UPDATE --------------
Still in the loop of login, verify, new password and login again. The screen I get is like this:
The following screens are:
enter code send by sms
Enter old and new password
Login
-. And back at the verify screen again.
Any suggestions.
Based on the suggestion below I also removed some of the credentials in the credential manager (those that I thought might have to do with this issue).
One possiblity is that there is an old version of your password stored in Credential Manager.
When you try to login via Visual Studio it fails because the password is incorrect. Trying to login with the incorrect password also causes the account to lock, requiring you to verify with SMS.
If this is an Azure WebApp, your best bet is to download the publish profile and use it in your Visual Studio, this way you'll be able to publish your app.
I have no problems building our app for the iOS simulator, with automatic bundle signing and the associated automatic provisioning profile. My settings are:
But my colleague gets this:
The system can't find a matching provisioning profile for the automatic signing identity.
What are we missing? My understanding is that he doesn't need an Apple Developer ID or to be part of our Apple Developer Team for automatic signing. Or am I wrong?
First he should check if he is logged in with his Apple ID to Visual Studio - he needs to have Apple Developer ID to have any kind of provisional profile signing.
But even then I don't think that it will work, App ID is unique so if your team owns it no one else can have the same and thus it can't be created on his Apple account.
Cause：
Since you are using Manual Provisioning, your colleague should download the provisioning profile and install on his computer.
Solution:
To login Apple account and download certifications with Visual Studio, go to tools --> options --> Xamarin --> Apple Account. If you are not login, you can add you apple ID here. After login, you can choose your app ID and then click View Detail button, you can see all the certifications you download or not download there.
Once your colleague download the provisioning profile and install properly, he will see the provisioning profile in his Visual Studio.
Refer: manual-provisioning?tabs=windows
I have just changed my Azure portal login password as it was about to expire in next 4 days. After this when I tried to deploy my cloud service VS 2013 ask "ReEnter Credentials your Credentials", After entering new credentials it keep asking me ReEnter your credentials also No subscription shows.
I tried to log in via Server Explorer also but the same problem occurs with Object Reference not set to an instance of an object error.
Can anyone have the solution of this?
Many thanks.
I have had this before on VS2015, the following worked for me:
Reboot and sign in (to ensure there are no processes locking relevant files)
Delete the folder %LOCALAPPDATA%.IdentityService
Go to Control Panel -> User Accounts -> Credential Manager and removing associated web and windows credentials
Delete the contents of %temp%
If that fails, try running Visual Studio as administrator and sign in again.
I use to sign-in to server explorer & query AzureTable entities.
However since I have updated to Visual Studio Update 4, I have not been able to login.
I tried using same credentials on azure portal & they work perfectly fine.
Visual Studio
Sorry, but we're having trouble signing you in
User account you used to sign in is not supported for this
application. Please use a different account to sign in.
To my surprise, Google did not return any relevant search result for this error.
P.S. I have double checked my Microsoft account credentials & they are working. This issue has been happening with other team members on different PCs as well.
I have learned to live with this error. This is definitely a bug in VS-2013 Update 4 which Microsoft should look into.
I use to sign-out from current subscription in Azure
Right click Azure in server explorer
Click Connect to Microsoft Azure Subscription
It works for one and only time. Next time repeat the process 1 to 3 again.
I believe I've had the exact same issue. Here's how I resolved it:
In the log-in page that "pops up" from Visual Studio I deleted the Microsoft account id that I usually sign in with and entered a different account ID that I own.
As soon as I finished typing the account id in, the page was refreshed and I was redirected to a Microsoft account log-in page. In that log-in page I made sure to type in the correct Microsoft account ID (the one I use for Azure) and its password. Having successfully signed in there, I was able to continue working as usual.
This was roughly based on guidance I found in this Microsoft Technet discussion.
Same here with Visual Studio 2015. I did logout user from visual studio and log in again and problem went away for good.
I recently received the same error after deploying an app to Azure and trying to connect to a DB server I had launched. When you first create an account, MS gives you a default active directory where you're sign in account is assigned the role of global administrator. You need to create a user account for this directory and use these credentials to sign in (different from signing into Visual Studio, you're providing credentials to access something on Azure).
In the Azure Portal, open up Active Directory and click on the default directory (or whichever one your project lives in). Go to the Users tab and select "Add User" from the panel at the bottom of the window. For "Type of User" select "New user in your organization", fill in the rest of the details and create the account. You get a temporary password and an awkward username. Now if you refresh server explorer you should be able to enter these credentials (and get prompted to enter a new password).
Just wanted to inform all of you that I had the same problem. Since this Sunday it disappeared magically on my VS 2013 Update 4 on all my machines. Here are my experiences:
Last week I had to re-enter my subscription after any VS-restart.
Sunday I opened VS and I was asked to reenter my VS-credentials in the upper-right corner.
I did not reenter my VS-credentials but simply expanded "Azure" in the Server Explorer and then expanded "SQL Databases" which led to the login-prompt formerly. Now the "Server Explorer" acted as expected.
I thought that the missing VS-login was the solution but I was wrong. Even with my VS logged on I know can restart the Studio as many times I want -> it works.
To ensure this I did several restarts of my machine too.
This is a stuff up on Microsoft's side, just replace your email address with one that isn't linked already and it will work.
To fix it: Use your a different email address with the same account through visual studio.