We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
There was an error while loading. Please reload this page.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
CocoaPods
When calling the method -callWithObject:completion: it throws an exception if the dictionary for the object contains an FIRTimestamp value.
-callWithObject:completion:
It should be able to encode this value.
Unsupported type: FIRTimestamp for value <FIRTimestamp: seconds=1605621091 nanoseconds=0>"
What happened? How can we make the problem occur?
FUNThrowInvalidArgument
FIRFunctions *functions = [FIRFunctions functions]; FIRHTTPSCallable *function = [functions HTTPSCallableWithName:@"myfunction"]; NSDictionary *object = @{@"postDate": [FIRTimestamp timestampWithDate:[NSDate now]]}; [function callWithObject:object completion:^(FIRHTTPSCallableResult * _Nullable result, NSError * _Nullable error) { }];
The text was updated successfully, but these errors were encountered:
I found a few problems with this issue:
Sorry, something went wrong.
@PomegranateApps Sorry for the trouble, but FirebaseFunctions does not support the FIRTimestamp type. There is an open feature request at #1738
FIRTimestamp
No branches or pull requests
[REQUIRED] Step 1: Describe your environment
CocoaPods
[REQUIRED] Step 2: Describe the problem
When calling the method
-callWithObject:completion:
it throws an exception if the dictionary for the object contains an FIRTimestamp value.It should be able to encode this value.
Unsupported type: FIRTimestamp for value <FIRTimestamp: seconds=1605621091 nanoseconds=0>"
Steps to reproduce:
What happened? How can we make the problem occur?
FUNThrowInvalidArgument
Relevant Code:
The text was updated successfully, but these errors were encountered: