07-29-2021
01:18
- last edited on
07-29-2021
03:32
by
JonFitbit
07-29-2021
01:18
- last edited on
07-29-2021
03:32
by
JonFitbit
@JonFitbit Hi Jon!
With new simulator 0.9.1 we got a problem of using outbox.enqueue().
In previous version (0.9.0) file was actually saved in folder /private/data.
In new version (0.9.1) file is saved in folder /stage. This folder is not accessible to the device.
We can't use simulator write now. Сan You tell us why this is happening?
Best Answer
Fitbit Developers oversee the SDK and API forums. We're here to answer questions about Fitbit developer tools, assist with projects, and make sure your voice is heard by the development team.
Fitbit Developers oversee the SDK and API forums. We're here to answer questions about Fitbit developer tools, assist with projects, and make sure your voice is heard by the development team.
Internal tests have all passed. Please can you delete your app from the simulator and try again?
Best Answer
Fitbit Developers oversee the SDK and API forums. We're here to answer questions about Fitbit developer tools, assist with projects, and make sure your voice is heard by the development team.
Also, which SDK version and are you using Windows or Mac?
Best Answer@JonFitbit Hi Jon!
Thank you for your attention.
SDK 5. The problem is on Windows 10x64 PC. I did some research on this issue. The other two PCs (Windows 10x64 and Windows 7x64) do not have this problem in the simulator. I compared the simulator log file (AppData\Roaming\Fitbit OS Simulator\logs\main.log) on the PC with the problem (Windows 10x64) and on the PC without the problem (Windows 7x64). Is the problem with syncRPC? What can I do additionally to understand the cause of the problem? On the PC with the problem (Windows 10x64), Windows system services RpcSs, RpcEptMapper, RpcLocator are enabled. Maybe other Windows system services should be enabled for syncRPC?
https://www.screencast.com/t/MsdBSqzZMCDp
Best Answer