View Single Post
Posts: 287 | Thanked: 862 times | Joined on Dec 2015
#365
Originally Posted by ruff View Post
Are you getting nacks starting from the very first packet (initialization) or for consequent data? i.e. the former would look strange as it means any upload should be failing, while the later is logicac if we're not using proper upload->type - eg. pebble just cannot parse incoming bytes in accordance with specified type and hence is failing and nacking the transfer.
I presume you've been trying with UploadTypeSystemResources? Did you try feeding the file to pbpack tool to check whether it's in proper binary resource format pebble understands?
I tried File and SystemResources. Have to manually calculate the CRC because it's not in the file, but I think it's right. I get the NACK after the upload is finished.

The timeline pin stuff is looking really good! That's exactly how Katharine said it should be, especially if we fetch the layout json from the pbz when we upgrade.