I am attempting to integrate Google Firebase's Cloud Firestore database into my application on Xamarin in Visual Studio for Mac. In order to do this I am using the Plugin.CloudFirestore and Plugin.FirebaseAuth NuGet packages. The issue is whenever I login or create an account using Plugin.FirebaseAuth I get the following error:
An error occurred when accessing the keychain. The #c NSLocalizedFailureReasonErrorKey field in the #c NSError.userInfo dictionary will contain more information about the error encountered.
It seems to be successfully making a call to the Firebase project as the user is created; however, I believe it is having an issue saving the authentication token/information locally. This error only happens on the iOS project. I do not even know where to start with this error because I cannot find the #c NSError.userInfo dictionary. If anyone knows where I can find that it would be a huge help.
Also if anyone knows how to fix this error that would be a huge help, but I assume the information in the aforementioned dictionary would be important to fixing this.
In that plugin, Plugin.FirebaseAuth, the UserInfo (NSErrorException based) is remapped to a plugin defined platform independent FirebaseAuthException class.
So look at Message property (and then the Reason property) of the thrown FirebaseAuthException as things are mapped in this exception class based upon the original Firebase error code.
Example: The Reason property contains a localized error message if the Firebase password is determined to be weak:
case AuthErrorCode.WeakPassword:
var reason = userInfo[NSError.LocalizedFailureReasonErrorKey] as NSString;
return new FirebaseAuthException(message, exception, ErrorType.WeakPassword, errorCode, reason);
case AuthErrorCode.EmailAlreadyInUse:
re: https://github.com/f-miyu/Plugin.FirebaseAuth/blob/b723d9d15d523a24cdfe34dee2353a6f67553756/Plugin.FirebaseAuth/iOS/ExceptionMapper.cs#L1
Related
I have a .Net Framework MVC app and I integrated DynamoDB.
When I enter on any page, until the page is fully loaded, I get many DynamoDB errors.
Does anyone know what the issue can be?
I checked a lot (found out that is related to Http Modules) but can not find any reason.
I have AWSSDK.Core (3.3.106.7) and AWSSDK.DynamoDBv2 (3.3.105.29) packages installed.
After some more investigation I find that the error is because some files are missing. Example:
Locating source for 'D:\JenkinsWorkspaces\trebuchet-stage-release\AWSDotNetPublic\sdk\src\Core\Amazon.Runtime\Pipeline\ErrorHandler\HttpErrorResponseExceptionHandler.cs'.
The file 'D:\JenkinsWorkspaces\trebuchet-stage-release\AWSDotNetPublic\sdk\src\Core\Amazon.Runtime\Pipeline\ErrorHandler\HttpErrorResponseExceptionHandler.cs' does not exist
But I don't even have a D:\ partition. Where is this coming from?
You're doing some operation with a condition expression and that condition isn't fulfilled, that's why you're getting a ConditionalCheckFailed exception.
From the docs:
ConditionalCheckFailedException
Message: The conditional request failed.
You specified a condition that evaluated to false. For example, you
might have tried to perform a conditional update on an item, but the
actual value of the attribute did not match the expected value in the
condition.
OK to retry? No
This is all I can tell you based on the amount of details (or lack thereof) you've provided.
I have a 2016 access file, when I try to access this file with an SQL or Access datasource in visual studio I get the following error message:
Database schema could not be retrieved for this connection. Please make sure the connection settings are correct and that the database is online.
The database you are trying to open requires a newer version of Microsoft Access
I checked my database and I don't have any Large Number in it so I'm not sure what exactly is the problem.
It was working fine before I did some changes with a few Date/Time data type but I since changed all the Date/Time to Short Text. I'm not certain if it has any relation to the error message but it was the only change I've made before the error.
Can anyone help?
I had this problem and its stems from the use of new data fields.
Eliminating them alone did not do the trick. When you use one of the new field types it steps the version up to 16.7, which is not compatible with earlier access versions.
Note that you can get the version number with ? Currentdb.Version in the immediate window
I had to run the compact and repair routine in order to get the version to step down.
If I add a new model version and then add an attribute to an entity I get a migration failure. It doesn't matter what the type of the attribute is or whether it is optional or has a default value. If I just add the new model version but don't add the attribute it works OK. I have done this sort of thing lots of times over the past 3 years without problems. Both NSMigratePersistentStoresAutomaticallyOption and NSInferMappingModelAutomaticallyOption are set to true. The error I get is shown below.
2018-02-18 12:28:51.771608+0000 Writing Shed[4105:1886727] [error] error: Illegal attempt to save to a file that was never opened. "This NSPersistentStoreCoordinator has no persistent stores (schema mismatch or migration failure). It cannot perform a save operation.". Last recorded error = Error Domain=NSCocoaErrorDomain Code=134140 "Persistent store migration failed, missing mapping model."
Does anyone know what might be wrong?
I've found the problem. I'm developing an app on Mac OS that is already available on IOS. They sync CoreData via iCloud. At some point while working on the Mac I added some attributes to the model that weren't optional or defaulted. To cut a long story short this caused problems with an IOS store that predated the changes, so that's when the migration failed (can't migrate to non-optional/non-defaulted attributes). I'm still not sure how I got into this situation because I'm usually very careful with CoreData, but hey stuff happens. Thanks for the comments which made me look deeper.
I am trying to integrate the power bi report with our asp.net mvc application. So I found this https://azure.microsoft.com/en-us/documentation/articles/power-bi-embedded-get-started-sample/ article and followed the steps. I have successfully created the workspace collection and generated the access keys. And I downloaded this https://github.com/Azure-Samples/power-bi-embedded-integrate-report-into-web-app/ sample application as specified in the article and ran the ProvisionSample contsole application. I selected the 5th step and provided the appropriate values for workspace collection name and access key and it throws the following error "Operation returned an invalid status code 'Forbidden'". I looked at the audit logs and there is no error. Anyone have idea what causes for this issue?
There is an issue going on right now that is effecting some parts of the world. We are actively working on a fix.
I am trying to set the assignee field to an existing issue in Jira using the Rest api call.
I am getting the error: "Field 'assignee' cannot be set. It is not on the appropriate screen, or unknown."
I am making a PUT call to "https//:{jira-server}/rest/api/2/issue/OPCP-32" where OPCP-32 is the issue id.
Is it an error related to permissions or am I doing anything wrong?
My json looks like this: http://pastebin.com/56TMMTCN
It was a permission related issue. Got the necessary permissions and it is working as expected.