Slightly improve logging around failed init conditions (#1000)

extension/data/init.ts

@@ -149,14 +149,26 @@ async function checkLoadConditions (tries = 3) {
     }
 
     // Check that we have details about the current user
-    const userDetails = await TBApi.getUserDetails();
+    let userDetails;
+    try {
+        userDetails = await TBApi.getUserDetails();
+    } catch (error) {
+        throw new Error('Failed to fetch user details', {cause: error});
+    }
     if (!userDetails || userDetails.constructor !== Object || !Object.keys(userDetails).length) {
-        throw new Error('Failed to fetch user details');
+        throw new Error(`Fetched user details are invalid: ${userDetails}`);
     }
 
     // Write a setting and read back its value, if this fails something is wrong
-    if (await TBStorage.setSettingAsync('Utils', 'echoTest', 'echo') !== 'echo') {
-        throw new Error('Settings cannot be read/written');
+    let echoValue = Math.random();
+    let echoResult: number;
+    try {
+        echoResult = await TBStorage.setSettingAsync('Utils', 'echoTest', echoValue);
+    } catch (error) {
+        throw new Error('Failed to write to settings', {cause: error});
+    }
+    if (echoResult !== echoValue) {
+        throw new Error(`Settings read/write inconsistent: expected ${echoValue}, received ${echoResult}`);
     }
 }
 

tsconfig.json

@@ -1,6 +1,7 @@
 {
     "extends": "@tsconfig/recommended/tsconfig.json",
     "compilerOptions": {
+        "target": "ESNext",
         "allowJs": true,
         // we only really care about rollup output, but if we leave this unset
         // then tooling will complain about the tsconfig.json being invalid