When users save a record in our apps I check if the feature can be updated, and if not I add the feature instead. In a recent app (100.5) we've noticed that if the user updates the (point) geometry canUpdateFeature is returning as false and triggering the creation of a duplicate feature in the geodatabase.
Is this the expected behavior? Should I be detecting an existing feature in another way?
This appears to be due to the new point being outside the replica extent. Not sure yet though because our users were definitely out inside the extent when editing field points and we got duplicate records.