Cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

Simulator outbox.enqueue() problem

@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
0 Votes
5 REPLIES 5

That's strange. The stage folder is a temporary folder that's used while the file transfer is in progress. I'll raise this with the tools team.

Best Answer

Thank you, Jon!

Best Answer
0 Votes

Internal tests have all passed. Please can you delete your app from the simulator and try again?

Best Answer
0 Votes

Also, which SDK version and are you using Windows or Mac?

Best Answer
0 Votes

@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

 

2021-07-30_17-41-28.png

Best Answer
0 Votes