Is there a builtin or standard way to apply a query.distinct query using the iOS SDK?
It is specifically listed in the JavaScript and Android API references. But not iOS.
I guess this means it is not implemented or supported? Yet - i.e. it may be an oversight right now? Or is there a reason it cannot be implemented on the platform?
And are there workarounds where I do not have to pull ALL the data down locally before processing / looping through the result set?
Distinct is not supported in the Parse iOS SDK (yet), because not every feature is implemented in all Parse client SKDs immediately, so it can take time until it trickles down into all SDKs.
Related
My team has a nativescript-vue application that is targeting the iOS platform. We were trying to uniquely identify the iOS device uuid via nativescript-uuid, but that appears to no longer supported. What is the best approach to use the DeviceCheck API?
You were right nativescript-uuid plugin is not updated to work with iOS 11 or later (DeviceCheck API).
An alternative could be using nativescript-secure-storage plugin, store the UUID you get using UIDevice.currentDevice.identifierForVendor.UUIDString for the first time, then it should return the same value even after reinstalling the app.
I'm in need of using the BotFramework SDK to build a bridge from Skype to Mattermost. As I understand it, we're pretty much limited to using the BotFramework to accomplish this via their SDK, however C# and Node.js are not really an option for this presently in this case. Is there a way to use Go already with the SDK or does some porting need to be done?
As for January 2020 an implemntation has been provided (not officialy by MS):
https://www.infracloud.io/microsoft-bot-framwework-sdk-for-go/
Recently i got a project which was build on Xamarin on Mac.Now, when i try to open this project on visual studio for MAC (As you all know Xamarin is now visual studio for MAC) it shows some errors regarding Monotouch.
The question is : Do i really need to convert app to unified API ? i know there is tutorial on official Xamarin doc to change app to unified API, but if there is any other way to open app without migrating to unified api.And what will be advantages and disadvantages of migration?
There are quite a few reasons why you might consider updating, but I will highlight some of the more important ones. Firstly consider that Apple as a manufacturer of hardware and software have always striven to keep their devices upto date, as such lagging behind as an iOS app developer can absolutely effect the demand for your app.
Firstly it already became a push or jump situation, as Xamarin stopped updating or supporting feature additions to their 'classic api' (As of writing we are on iOS 10.3).
The complete removal of classic support is scheduled for next fall
with the release of Xamarin.iOS 10.0.
Secondly the unified API is required to meet apples desire to support 64bit architecture:
The new Unified APIs are required to support 64 bit device
architectures from a Xamarin.iOS mobile application. As of February
1st, 2015 Apple requires that all new app submissions to the iTunes
App Store support 64 bit architectures.
As to your concern regarding the dissadvantages, I will simply say that the migration can either go smoothly, or not so smoothly. It's worth bearing in mind that the 'unified api' uses different native data types which may require some work arounds depending on the current structure of your original code.
The biggest point is what I mentioned earlier, in Apples App Store if you linger behind in terms of keeping your app up to date with the latest SDK, API, or anything else Apple decide to upgrade, then it is akin to giving up on that application.
I've put together some links below that may aid you in the migration process:
Native Types - Describes the new native data types that you will need to use in a Unified API app.
32/64 bit Platform Considerations - Considerations in choosing 32-bit and 64-bit modes for your application.
Updating Existing iOS Apps - Follow these steps to update an existing Xamarin.iOS app to use the Unified API.
Binding Objective-C Libraries - This document describes the process used to create C# bindings of Objective-C APIs and how the idioms in Objective-C are mapped to the idioms used in .NET.If you are binding just C APIs, you should use the standard .NET mechanism for this, the P/Invoke framework.
Binding Definition Reference Guide - This is the reference guide that describes all of the attributes available to binding authors to drive the binding generation process.
Updating UI Components - This is a guide to the process for updating UI componenets to the latest versions within the unified api.
We want to transfer data from a client to a server in realtime, so we have decided to go with WebSockets.
Using Xamarin.Forms it was surprisingly difficult to find a suitable WebSocket library.
The best match was "WebSocket4Net" because it is directly suggested on Xamarin's Homepage. However I was not able to install this library, because it only supports versions of .NET up to v4.0. (We are using v4.5)
Whenever I try to change the target framework of my PCLs from v4.5 to v4.0 I get loads of weird errors stating "Windows.Input library could not be found", "ObservableCollection could not be found" etc.
So we are currently using the library "WebSocket.Portable.Core", which although lacking some functionality worked out. However for some reason we can only receive one message. The event "MessageReceived" always is just called once.
Has anyone heard about such a problem with WebSockets? Maybe it is just time to use another library, but I just can't find one?
I also can't find any solution how to implement WebSockets natively for each platform.
WebSockets.PCL has a native implementation for each platform and it's well documented
https://github.com/NVentimiglia/WebSockets.Pcl
Where do you find out if Android, Safari (iOs) etc are supported by the Google Closure libraries?
GCL supports all of them. That is the nice thing about GCL, a platform independent Library, that abstracts nasty platform/browser specific bugs.
I found the following way to search the source code, where you can look for words like iPhone etc to see what specific handling they have for specific devices.
Code search for iphone: http://www.google.com/codesearch#search/&q=iphone%20package:http://closure-library%5C.googlecode%5C.com
Although searching for blackberry doesn't return anything, which means that it doesn't cater for Blackberry's Javascript?