As mentioned in my previous post, there were a couple of issues I had to resolve to release the initial version of Blurtkey.

My objective/goal for this app is to release its initial version to Google Play. I still have a couple of items I need to resolve before releasing it's initial version. Particularly items #2 and #3 below.

1. No loading indication after clicking import in the account import > page (no indication or feedback to user that import is processing)
2. Forever loading icon on wallet page (latest wallet transaction not retrieved)
3. Wallet operations are not working
   1. Delegate

For this update, I'm sharing how I was able to resolve item #2 above.

Forever loading icon on wallet page (latest wallet transaction not retrieved)

P.S.
We're in a holiday right now, as such, I am able to provide these frequent updates. When holidays are over, my updates will be infrequent.

1. Background

When trying to resolve issues, one of the most important step is diagnosing the problem and identifying the root cause. Because of the cognitive load I had to dedicate to work, I didn't have the capacity to consciously think of ways to troubleshoot and find out the root cause as early as I want.

2. Troubleshooting (aka Debugging)

The first step I had to make was identify the possible lines of codes that was causing the issue. I've already identified beforehand that the problem occurs in the Transactions component. It had to do with fetching the transactions.

Next, I've identified that the problem was happening inside the initAccountTransactions and fetchAccountTransactions actions. The previous change (renaming hive to blurt) helped me in identifying this location. I've identified that getting an account's transactions was happening in the getAccountTransactions method. It had this block of code.

    const transactions = await getClient().database.getAccountHistory(
      accountName,
      start || -1,
      start ? Math.min(10, start) : 1000,
      operationsBitmask,
    );

I've identified that the error was happening in this block of code by placing console logs before and after this block. I enclosed it in a try-catch statement and logged the error.

The enclosing try-catch gave me this following error which gave me the hint as to what was causing the problem.

RPCError: args.size() == 3: Expected #s argument(s), was 5

At first, I was really not sure what the error was saying since I was expecting that the library I was using was working. But eventually, it led to the conclusion that the problem was indeed in the library I was using - dblurt.

3. The Solution

Since I don't have access to the official dblurt library, I cloned the codes from blurt's repo, made my changes there, and published it as a scoped npm package.

This is an important step because time is of the essence when troubleshooting or debugging issues. It's important to not lose momentum.

The interim solution was this block of code:

  public getAccountHistory(
    account: string,
    from: number,
    limit: number,
    operation_bitmask?: [number, number]
  ): Promise<[[number, AppliedOperation]]> {
    let params = [account, from, limit]
    /*
    if (operation_bitmask && Array.isArray(operation_bitmask)) {
      if (operation_bitmask.length !== 2) {
        throw Error(
          'operation_bitmask should be generated by the helper function'
        )
      }
      params = params.concat(operation_bitmask)
    }
    */
    console.log("this.call('get_account_history', params)", params)
    return this.call('get_account_history', params)
  }

I commented out the portion where it adds to the params[] array the operation_bitmask. The error I logged from the previous section gave me the confidence that it will solve the problem since the operation_bitmask is what gets added to the paramaters. params[] has an initial size of 3 (account, from, and limit), but adding operation_bitmask increases the size of the array which resulted to the error.

RPCError: args.size() == 3: Expected #s argument(s), was 5

4. Key Take-aways

Overall, this is how I troubleshoot issues.

1. Identify which block of code causes the error
2. Output the specific error that the lines of code output (this is where the importance of libraries spitting out descriptive error messages)
3. Try out solutions based on the error outputted
4. Take a break if root cause cannot be immediately identified (taking more than two hours of continuous debugging).

5. Demo

Demo of the transactions loading successfully in the wallet page.

6. Codes

Code changes are available in Blurtopian's repository:

https://gitlab.com/blurtopian/blurtlibs/dblurt

7. NPM Package

https://www.npmjs.com/package/@blurtopian/dblurt

8. Next

My objective/goal for this app is to release its initial version to Google Play. I still have a couple of items I need to resolve before releasing it's initial version. Particularly items #2 and #3 below.

1. No loading indication after clicking import in the account import page (no indication or feedback to user that import is processing)
2. Forever loading icon on wallet page (latest wallet transaction not retrieved) (Resolved)
3. Wallet operations are not working
   1. Delegate

---

@eastmael's Witness Projects

• Blurtkey the mobile Keychain version for Blurt (This Update)
• Blurt Wallet Modifications
• https://blurt-now.com/ to monitor your Blurt account
• @brunobot a Blurt Discord Bot notification service
• Blurt + Dtube Integration to simultaneously post your video on DTube and Blurt
• Blurt Richlist API in coordination with @ecosynthesizer's Blurt Richlist UI
• https://bi.blurt-now.com/ for your Blurt Business Intelligence data needs
• https://blurtopian.com @blurtopian #blurtopian Blurt contribution curation initiative

---

Find my contributions valuable? Please consider voting for my witness:

https://blurtwallet.com/~witnesses?highlight=eastmael