Is there a way to rebuild Dexie keys?

This seems to be an update bug in Safari and should really be posted to bugs.webkit.org. Let's assume it gets fixed there, as the Safari team is very responsive when it comes to critical bugs. Please register it!

As for a workaround, I would suggest recreating the database. Copy the database to the new database, delete it, then copy and delete the intermediate copy. I have not tested the code below, so you need to test it.

function check_and_fix_IOS_10_3_upgrade_issue () {
    return (somehowCheckIfWeNeedToDoThis) ?
        recreateDatabase() : Promise.resolve();
}

function recreateDatabase () {
    copyDatabase("dbName", "dbName_tmp").then(()=>{
        return Dexie.delete("dbName");
    }).then(()=>{
        return copyDatabase("dbName_tmp", "dbName");
    }).then(()=>{
        return Dexie.delete("dbName_tmp");
    });
}

function copyDatabase(fromDbName, toDbName) {
    return new Dexie(fromDbName).open().then(db => {
        let schema = db.tables.reduce((schema, table) => {
            schema[table.name] = [table.schema.primKey.src]
                .concat(table.schema.indexes.map(idx => idx.src))
                .join(',');
        }, {});

        let dbCopy = new Dexie(toDbName);
        dbCopy.version(db.verno).stores(schema);

        return dbCopy.open().then(()=>{
            // dbCopy is now successfully created with same version and schema as source db.
            // Now also copy the data
            return Promise.all(
                db.tables.map(table =>
                    table.toArray().then(rows => dbCopy.table(table.name).bulkAdd(rows))));
        }).finally(()=>{
             db.close();
             dbCopy.close();
        });
    })
}

      

        
        
        
      

    

As far as "somehowCheckIfWeNeedToDoThis" is concerned, I cannot answer exactly how to do it. Maybe user agent sniff + cookie (set a persistent cookie when fixed so it doesn't get recreated over and over). Perhaps you can find a better solution.

Then, before opening your database (perhaps before starting your application), you need to do something like:

check_and_fix_IOS_10_3_upgrade_issue()
    .then(()=>app.start())
    .catch(err => {
        // Display error, to user
    });