UnsuportedOperationException: JsonNull

Good evening,

I was just ending a pack for my daughter (on windows) when I had an issue on transfering to the lunii. Logs : 2020-04-24 23:41:27,422 [WARN ] [s.w.s.LibraryService]: Pack to transfer is in archive format. Converting to binary format and storing in temporary file: C:\Users\Adrien\AppData\Local\Temp\Triforce-6470d48c-a0eb-4875-8101-1b95afb3ad96-v1.zip1591689213836808193.pack 2020-04-24 23:41:27,424 [WARN ] [s.w.s.LibraryService]: Reading archive format pack Exception in thread "Timer-4" java.lang.UnsupportedOperationException: JsonNull at com.google.gson.JsonElement.getAsString(JsonElement.java:192) at studio.core.v1.reader.archive.ArchiveStoryPackReader.read(ArchiveStoryPackReader.java:170) at studio.webui.service.LibraryService.getBinaryPackFile(LibraryService.java:127) at studio.webui.api.DeviceController$1.run(DeviceController.java:66) at java.base/java.util.TimerThread.mainLoop(Timer.java:556) at java.base/java.util.TimerThread.run(Timer.java:506)

Maybe not linked but I am unable to set my official.json file because I have this return from lunii API when I give token : < HTTP/1.1 401 Unauthorized < Server: nginx < Date: Fri, 24 Apr 2020 21:56:17 GMT < Content-Type: application/json; charset=utf-8 < Content-Length: 48 < Connection: keep-alive < Access-Control-Allow-Origin: * < Cache-Control: no-cache < Strict-Transport-Security: max-age=31556926; includeSubDomains; preload < { "error" : "Unable to validate signature." }

This with the token I have in “C:\Users\USER\AppData\Roaming\Luniitheque.local.properties” And the file is like :

#Fri Apr 24 23:53:07 CEST 2020
token={"firebase"\:"TOKEN"}
remember_me=0

Not the same thing I can see in your README (tokens.access_tokens.data.firebase)

Triforce-6470d48c-a0eb-4875-8101-1b95afb3ad96-v1.zip

Can you help me with that please ? Thanks a lot !

[bourgouinadrien]

@marian-m12l works like a charm ! Thanks a lot dude 😃

[marian-m12l]

There was indeed an embarrassing bug when using “backwards” links (created from to destination). Now fixed with release 0.1.14