Skip to content

could not determine pgpType #633

Closed
Closed

Description

@tomholub
[STACK_TRACE]
com.flowcrypt.email.util.exception.ManualHandledException: Handled manually:
        at com.flowcrypt.email.util.exception.ExceptionUtil$Companion.handleError(ExceptionUtil.kt:30)
        at com.flowcrypt.email.ui.loader.ParseKeysFromResourceAsyncTaskLoader.loadInBackground(ParseKeysFromResourceAsyncTaskLoader.kt:73)
        at com.flowcrypt.email.ui.loader.ParseKeysFromResourceAsyncTaskLoader.loadInBackground(ParseKeysFromResourceAsyncTaskLoader.kt:30)
        at androidx.loader.content.AsyncTaskLoader.onLoadInBackground(AsyncTaskLoader.java:307)
        at androidx.loader.content.AsyncTaskLoader$LoadTask.doInBackground(AsyncTaskLoader.java:60)
        at androidx.loader.content.AsyncTaskLoader$LoadTask.doInBackground(AsyncTaskLoader.java:48)
        at androidx.loader.content.ModernAsyncTask$2.call(ModernAsyncTask.java:141)
        at java.util.concurrent.FutureTask.run(FutureTask.java:266)
        at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1167)
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:641)
        at java.lang.Thread.run(Thread.java:764)
Caused by: com.flowcrypt.email.util.exception.NodeException: Error :Cannot parse key: could not determine pgpType
Stack :null
Type :null
        at com.flowcrypt.email.api.retrofit.node.NodeCallsExecutor$Companion.checkResult(NodeCallsExecutor.kt:189)
        at com.flowcrypt.email.api.retrofit.node.NodeCallsExecutor$Companion.parseKeys(NodeCallsExecutor.kt:53)
        at com.flowcrypt.email.ui.loader.ParseKeysFromResourceAsyncTaskLoader.loadInBackground(ParseKeysFromResourceAsyncTaskLoader.kt:68)
        ... 9 more
com.flowcrypt.email.util.exception.NodeException: Error :Cannot parse key: could not determine pgpType
Stack :null
Type :null
        at com.flowcrypt.email.api.retrofit.node.NodeCallsExecutor$Companion.checkResult(NodeCallsExecutor.kt:189)
        at com.flowcrypt.email.api.retrofit.node.NodeCallsExecutor$Companion.parseKeys(NodeCallsExecutor.kt:53)
        at com.flowcrypt.email.ui.loader.ParseKeysFromResourceAsyncTaskLoader.loadInBackground(ParseKeysFromResourceAsyncTaskLoader.kt:68)
        at com.flowcrypt.email.ui.loader.ParseKeysFromResourceAsyncTaskLoader.loadInBackground(ParseKeysFromResourceAsyncTaskLoader.kt:30)
        at androidx.loader.content.AsyncTaskLoader.onLoadInBackground(AsyncTaskLoader.java:307)
        at androidx.loader.content.AsyncTaskLoader$LoadTask.doInBackground(AsyncTaskLoader.java:60)
        at androidx.loader.content.AsyncTaskLoader$LoadTask.doInBackground(AsyncTaskLoader.java:48)
        at androidx.loader.content.ModernAsyncTask$2.call(ModernAsyncTask.java:141)
        at java.util.concurrent.FutureTask.run(FutureTask.java:266)
        at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1167)
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:641)
        at java.lang.Thread.run(Thread.java:764)

Activity

  1. added this to the 0.8.2 milestone on Jul 3, 2019
  2. self-assigned this
    on Jul 3, 2019
  3. tomholub commented on Jul 3, 2019

    @tomholub
    CollaboratorAuthor

    @DenBond7 This happens when supplied key to parseKeys is not a valid key.

    { format: "unknown", keyDetails: [], error: { message: "Cannot parse key: could not determine pgpType" } }

    I could skip the error and just return an empty result set:

    { format: "unknown", keyDetails: [] }
  4. DenBond7 commented on Jul 10, 2019

    @DenBond7
    Collaborator

    @tomholub

    I could skip the error and just return an empty result set:

    I think It'll be the best option. Then the app will show info: The content of your file does not look like a valid PGP %1$s Key. (%1$s = Private or Public). We had this logic before

  5. tomholub commented on Jul 10, 2019

    @tomholub
    CollaboratorAuthor

    Ok I'll to that.

  6. removed their assignment
    on Jul 10, 2019
  7. tomholub commented on Jul 10, 2019

    @tomholub
    CollaboratorAuthor

    See if this works better

  8. DenBond7 commented on Jul 11, 2019

    @DenBond7
    Collaborator

    I'm closing it. It works well

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

Type

No type

Projects

No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions