I checked in the C++ SDK official GitHub repository of Evernote createOrUpdateNotebookShares function in NoteStore is not available till now.
when this support will come for c++ SDK.
Related
I have been using Google.Cloud.Translation.V2 in a UWP app for a while. Its latest NuGet package is 3.1.0. Upgrading from 2.x to 3.x results in the following error:
NU1202: Package Google.Cloud.Translation.V2 3.1.0 is not compatible
with uap10.0.19041 (UAP,Version=v10.0.19041) / win10-x64-aot. Package
Google.Cloud.Translation.V2 3.1.0 supports:
net462 (.NETFramework,Version=v4.6.2)
netstandard2.1 (.NETStandard,Version=v2.1)
Does this mean the newer versions will no longer work with UWP apps?
Does this mean the newer versions will no longer work with UWP apps?
TLDR; UWP is not a supported platform
From this GitHub issue:
We don't currently support UWP, and even if using grpc-dotnet makes it technical work, it's unlikely that we will prioritize UWP support over other work. So when we have moved over to grpc-dotnet by default, you may be in a situation where you can try to use the libraries and quite possibly be successful, but we would still not support it.
Also shown in this comment:
To reiterate: UWP is not a supported platform for these libraries. You could potentially use the Google.Apis.* NuGet packages, which don't use gRPC, but again, UWP isn't a supported platform for those either.
Final note (from this comment):
You may find that the REST-based libraries for whichever APIs you're using (packages starting "Google.Apis") work, but again those aren't actually supported on UWP.
We are going to use Firebase C++ SDK for multiple projects, but we are not using cocoapods so we are manually downloading the Firebase SDKs as pointed out in the documentation from here:
https://firebase.google.com/docs/ios/setup#frameworks
https://firebase.google.com/docs/cpp/setup#available_libraries
The Firebase readme file from the downloaded C++ SDK (readme.md) states the following:
Important: Each version of the Firebase C++ SDK supports a specific version of the Firebase iOS SDK. Please ensure that you reference the Cocoapod versions listed above.
The download link from the documentation doesn't have multiple links for each version.
Edit: modified text and images with correct versions
Is there a place where we can download specific versions of the SKDs?
How can we make sure that the download versions are compatible with each other?
Just downloaded both sdks and from the readme:
- C++ SDK is version 5.6.1 and requires Firebase/Core Cocoapod (5.20.0)
- Objective-C SDK has Firebase version 5.20.2
The Objective-C library is a bigger version then requirement of the C++ one (5.20.2 > 5.20.0) but is this property enough to assure compatibility?
See below images for readmes:
readme.md - C++ SDK
README.md - Objective-C SDK
First off it seems that Google forgot to make a branch for the iOS version 5.20.2 (on git currently only this exists: https://github.com/firebase/firebase-ios-sdk/tree/release-5.20.0 )
Considering that only the last number was incremented, let's assume there aren't big changes between the two versions, so we can check 5.20.0.
Your issue is that in the C++ SDK's readme for the iOS part they don't specify exactly the obj-c counterparts but the pods version. You can use the pods files though to check if the versions correspond.
For example we can check "Firebase Auth": in the C++ SDK says that it uses the 5.20.0 pod for ios, which is this one: https://github.com/firebase/firebase-ios-sdk/blob/release-5.20.0/FirebaseAuth.podspec
FirebaseAuth.podspec
We can see in the file that the version of Firebase Auth for the obj-c 5.20.0 SDK is 5.4.2, as it is in your readme.
You can do the same for all necessary services to make sure the compatibility is maintained.
I have no idea unfortunately if you can check this in an automatic way.
When reading through the docs I found that updatePhoneNumber is not implemented in react-native-firebase.
The following methods are not supported in RNFirebase as they cannot work in the React Native environment or have a different implementation.
So how would I implement this specific method?
#Salakar from the react-native-firebase team here - support for updatePhoneNumber is landing in the upcoming v5.0.0 release of react-native-firebase.
If you need this sooner and are ok with using a release candidate version of the library then there should be another v5 RC version published by the end of next week with this change included (v5.0.0-rc2) - keep an eye out on discord for an announcement or the releases page on GitHub.
I want to rewrite my old .net app based on FirebAse with the new C++ SDK, I have managed to link and compile the libraries in my VS2015 environment, but now have no idea about how to use them.
The firebase quick start here:
https://github.com/firebase/quickstart-cpp/tree/master/auth/testapp/src/desktop
doesn't really show anything.
Am I looking in the wrong place?
Cheers.
Firebase C++ only provides stub libraries as a convenience for desktop at the moment so while you'll be able to link the libraries they won't actually do anything. We have a desktop implementation of our light platform abstraction layer for internal testing only - notice we don't ship desktop MSVC or Xcode projects.
See the readme.md in the Firebase SDK zip file for more information.
Our company's svn cannot allow single file larger than 40mb, realm framework needs 140mb+，so how can I build realm-cocoa with source code on github?
You could instead use the dynamic framework, which is a lot smaller (28,5 MB), through being already linked, but you won't be able to support iOS 7 in that way.
Alternatively I would recommend using a dependency manager like CocoaPods, which helps you with the setup and integration. But as a Core Member of this project, I'm obviously biased in that regard.
If that shouldn't be available for you, then you could theoretically use SVN externals to checkout the realm-cocoa repo (GitHub supports SVN transports), add the Realm.xcodeproj to your Xcode project, set the iOS framework target as dependency target of your app target and link to Realm.framework. But please not that this is not an officially supported way of integration.