You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This would enable developers to configure a new Cosmos DB database for use with the Data service. Users will be required to connect their app to an azure subscription and then enter a resource name, database location, and the desired throughput for pricing. Doing so will enable the developer to start using the Data service with their newly configured database.
Here are the latest iteration of the designs for this feature:
Let us know if you have any feedback, or would like to be a part of our private preview!
The text was updated successfully, but these errors were encountered:
it looks like App Center is not able to keep the relation with the newly created CosmosDB.
Once it is visible as fully created on Azure, it doesn't show properly on App Center
and it returns an error when called from Xamarin.Forms:
Microsoft.AppCenter.Data.DataException: com.microsoft.appcenter.data.exception.DataException: Call to App Center Token Exchange Service succeeded but the resulting payload indicates a failed state: {"tokens":[{"partition":"user","dbAccount":null,"dbName":null,"dbCollectionName":null,"token":null,"expiresOn":null,"accountId":null,"status":"Unauthenticated"}]}
Hello, it looks like it depends on the fact that the AppCenter user is not able to see the CosmosDB. When I used the same user on both AppCenter and Azure, it worked fine
Awesome, glad this issue was resolved. Seems to be the same issue in our other thread. Going to close this! Feel free to open a new issue if you have feature requests, bugs, or general feedback!
Data MVP Technical Specification
This would enable developers to configure a new Cosmos DB database for use with the Data service. Users will be required to connect their app to an azure subscription and then enter a resource name, database location, and the desired throughput for pricing. Doing so will enable the developer to start using the Data service with their newly configured database.
Here are the latest iteration of the designs for this feature:
Let us know if you have any feedback, or would like to be a part of our private preview!
The text was updated successfully, but these errors were encountered: