Deleted row (Primary key) on the server causes conflict when client adds new record

Hi - Iam using dotmim to sync a sqlite client with a sql server database. When I delete a row in management studio. A cannot add any records from the client in the same table (upload 1, conflict 1). I am guessing there is a primary key conflict, as the primary key that the client is trying to use is not acceptable to sql server. Is there a simple fix? Can I set sql server to reseed? or are UniqueIdentifiers/Guids the way forward? Thanks in advance - Pete ` var serverProvider = new SqlSyncChangeTrackingProvider(@“connectionstring;”);

    var clientProvider = new SqliteSyncProvider("Record.db3");

    var agent = new SyncAgent(clientProvider, serverProvider, new string[] { "Answer", "Question", "Response", 
   "ResponseType", "Site" });

    var syncContext = await agent.SynchronizeAsync(SyncType.ReinitializeWithUpload);`

[VagueGit]

We use integer primary keys as below. This is adequate for many use cases (Google/Facebook wouldn’t do it this way).

It will usually result in less fragmentation, less disk space, faster CRUD on the server than guids/uuids.

public static Int64 NewId
{// A loop that calls DateTimeOffset.Now.UtcTicks 10 times will return 7 distinct values (3 dupes) so we check for dupes
// This method will advance ~15 UtcTicks in 10 iterations and guarantees uniqueness.
// It is almost twice as fast as a while loop with SpinWait.SpinOnce();
// So this method will return a unique value appox every 1.5 milliseconds
    get
    {
        Int64 start = DateTimeOffset.Now.UtcTicks;
        Int64 end = DateTimeOffset.Now.UtcTicks;
        while (end == start)
            end = DateTimeOffset.Now.UtcTicks;
        return end;
    }
}

I welcome constructive critique

[PeterJey]

For the moment iam using int i = Guid.NewGuid().GetHashCode();