syncable

It seems you're equivocating on the word "optional". The word "optional" in the attribute description optional="YES" is not the same as, and has nothing to do with, the Swift Optional enum type.

The former is merely the ordinary English word "optional", meaning "not required" — for a particular entity, there might or might not be a value for this attribute, which is a Float, but even if there isn't, it's a valid entity. Nothing in the story says that this attribute's type is Optional. Its type is Float. And you can't assign a Swift Optional where its wrapped type is expected; you have to unwrap it.

Indeed, this point is made very explicitly by the documentation:

Optional attributes aren’t required to have a value when saved to the persistent store. Attributes are optional by default. Core Data optionals aren’t the same as Swift optionals. [My italics.]

We tweaked your idea and came up with this (in Kotlin, see below for Java):

It is sort of broken. I'm not really sure what was design intend but it feels really strange now.

Documentation of the prop clearly states error: Puts the input in a manual error state.

Lets look at the implementation

1. It is clear component should always report as invalid when this prop is set to true. OK
2. update:error event with value of true is send when some of the rules are broken. Doesn't make sense at all. If prop is intended for user to set error state manually, why firing update event as a result of validation ?
3. If you fix issue with field, update:error with value false is not send because it's blocked by error prop with value true. wtf?

So using error.sync absolutely doesn't make sense. It's an error in documentation at best. Bad design if you ask me. There should be some other event, with different name dedicated for communicating the validation state of the field...

One way would be to not pass error prop to field at all and just use the event:

I've figured this out as soon as I wrote my question.

The provider tag was introduced by cordova-plugin-mauron85-background-geolocation. The line android:authorities="@string/content_authority" says that the authorities value is defined in a string (variable) called content_authority. You will find the variable defined in your config.xml and 'packgage.json':

EDIT As @pskink pointed out in the comments, the problem is the query.

The problem lies in the query:

The sample uses 'nodejs-websocket'. In your server-code you are using 'ws' wich is another package. Try using the sample as it is, but add a package.json to it.

Could you not maybe do something like this:

I recently had a similar issue with Fortify. As Silvia Ragui pointed out Fortify doesn't analyze this runtime process correctly. While installIfNeeded() and installIfNeededAsync() will update the security provider in real world deployment of your APK, but it does not seem to clear the error when you resubmit to Fortify.

However the underlying issue is the out of date Security Provider which is usually due an out of date play services library in your package.

Here is the recommendation directly from fortify dashboard:

Android relies on the security Provider to provide secure network communications. The default device cryptographic libraries are typically older versions of OpenSSL that contain known flaws. To overcome this, Google provides a mechanism for an application to “patch” their local copy of OpenSSL via the Google Play Services ProviderInstaller client. It’s been determined that the app is not using the updated provider, leaving the application exposed to older known OpenSSL vulnerabilities and weaknesses.>

The actual problem is the same as the last line in Silvia's logs:

W/GooglePlayServicesUtil Google Play services out of date

In our case we updated to the latest version of Play Services in our package as well as implementing the fix above (when we did so we found there was small error that had to be fixed, and was probably preventing the update from patching the Security Provider)

The new build successfully cleared the issue. I suggest you update you to the latest Play Services as this will also update the Security Provider.

I found the problem. When I call accountManager.addAccount(..) or accountManager.removeAccount(..) or accountManager.setPassword, it cause to call syncAdapter.onPerformSync(..) at then sendRequest to server , ... . It causeses infinity loop. I solved the issue with adding extras to Bundle when calling ContentResolver