Error when executing two times

[herculosh]

Hi
I,m trying your script and be impressed. Nice idea.

When i start Skype for Business 2015 and execute

Start-Pomodoro -Minutes 1 -EndPersonalNote "Testing...

everything works fine. Great, thanks a lot.

C:\Users\myuser> Start-Pomodoro -Minutes 1 -EndPersonalNote "Testing...
WARNING: Skype for Business client is not running or signed in, no action was performed
Updated Skype for Business client status to custom activity 1 (Pomodoro Sprint) and personal note: Getting stuff done, will be available at 09:49

But the second time it failes and unfortunatly I cant find the issue.

C:\Users\myuser> Start-Pomodoro -Minutes 1 -EndPersonalNote "Testing..."

Exception calling "BeginPublishContactInformation" with "3" argument(s): ""
At C:\Users\myuser\Documents\WindowsPowerShell\Modules\PSProductivityTools\Functions\Publish-SfBContactInformation.ps1:
115 char:13
+             $Publish = $Self.BeginPublishContactInformation($ContactI ...
+             ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : NotSpecified: (:) [], MethodInvocationException
    + FullyQualifiedErrorId : ItemNotFoundException

Exception calling "EndPublishContactInformation" with "1" argument(s): "Invalid asyncResult"
At C:\Users\myuser\Documents\WindowsPowerShell\Modules\PSProductivityTools\Functions\Publish-SfBContactInformation.ps1:
116 char:13
+             $self.EndPublishContactInformation($Publish)
+             ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : NotSpecified: (:) [], MethodInvocationException
    + FullyQualifiedErrorId : ArgumentException



Updated Skype for Business client status to custom activity 1 (Pomodoro Sprint) and personal note: Getting stuff done, will be available at 09:45
Pomodoro sprint session ended, set status: Available and personal note: Testing...
C:\Users\myuser>

Do you have any hint where the problem could be?

TIA Ivo

[janegilring]

Hopefully fixed by commit 0a2986e

Could you run Update-Module -Name PSProductivityTools, restart PowerShell and see if the problem still occurs?