AEM Mobile Packager error on macOS High Sierra

[#1]

Since upgrading to macOS High Sierra, I have been unable to package articles using the AEM Mobile Packager tool -- on each packaging attempt, it crashes with a Go runtime error, as shown:

This used to happen occasionally for me on macOS Sierra, but now this error occurs on every single packaging attempt.

When can we expect updated tooling that has been tested on High Sierra to be released?

[#2 · Accepted solution]

Hi there,

Thanks for letting us know that this isn't working as expected. We will investigate and update this thread with an expected release date.

-

Darren

[#3]

Installation and setup for AEM Mobile tools has been updated with a version of the packager that now support High-Sierra.

[#4]

Great news, thanks very much!

[#5]

Hi verbrobinnorth​

We are hopeful to have a fix released next week - I will post here when it's made public.

Thanks for your patience.

-

Darren

[#6]

Hi Darren Melanson​, thanks for the quick reply. FWIW, it might just be that the tool needs recompiling against an updated version of Go -- there's a host of similar-sounding issues on the Go GitHub issues tracker: https://github.com/golang/go/search?utf8=%E2%9C%93&q=MSpanList_Insert+macOS&type=Issues

Please do keep me posted on progress -- I'm having to rely on a Windows virtual machine to use the packager tool at present.

Thanks!

[#7]

Thanks very much Darren Melanson​, I can confirm that it works for me on High Sierra too, which is great!

Only one thing -- I noticed that the download for the packager tool linked to from the UK version of the support page (https://helpx.adobe.com/uk/digital-publishing-solution/help/install.html) still points to the old version, so I imagine this means that other localised support pages are also still pointing to the old version too.

[#8]

Excellent I can confirm it works on 10.13! Thanks very much

[#9]

Waiting to hear on this issue as well. Thank you.

[#10]

Hi there, any update on timing for the fix? Thanks

[#11]

Hi Darren Melanson​, is there any ETA on a fix for this issue yet? Thanks!