Skip to content

initCallBack called with no error during digidoc::initialize if TSL downloading failed #694

@fl-ido

Description

@fl-ido

Hello,

I see that initialize function takes an optional initCallBack as a parameter which, according to the documentation, is called "when background thread TSL loading is completed" and takes as a parameter a "digidoc::Exception that occured on initialization".

My use case is the following : on Windows, I flush the %APPDATA%\digidocpp\tsl folder, in order to force the TSL lists downloading on the next digidoc initialization. Then, I initialize digidoc with a callback and with invalid proxy settings in the configuration, and I can see that TSL downloading actually fails (empty file is created in %APPDATA%\digidocpp\tsl folder). So, in this case I am expecting my callback to be called with an exception (like NetworkError for instance). But my callback is called with nullptr.

Am I misunderstanding something with the purpose of this callback ?

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions