App Name: Fubo App Link on Amazon Appstore (found through Developer Console > Actions column in App List > View on Amazon.com): Your App Link
Trying to set the timezone for vega simulator.
Run Simulator
Open Terminal
Run the following command: vega exec vda shell
Try to change timezone to New York: vdcm set com.amazon.devconf/system/configuration/time-zone 'America/New_York'
Receive error:
Could not set value for 'com.amazon.devconf/system/configuration/time-zone': No permission for operation
The previously resolution in this post no longer works to set permissions as it applies to kepler. There’s currently no list of steps to follow to set permissions on the files that would need to be changed. What are the instructions for vega simulator?
Active SDK Version: 0.22.5850
Vega CLI Version: 1.2.16
To set timezone for your app launch: vega device run-cmd -c "export TZ=America/New_York && your-app-launch-command"
Common timezone examples:
America/Los_Angeles (PST/PDT)
America/New_York (EST/EDT)
Europe/London (GMT/BST)
Asia/Kolkata (IST)
UTC
Note: The vdcm set command for timezone configuration requires system permissions that are not available in the simulator environment. The TZ environment variable approach is the recommended workaround for development and testing purposes.
This is a hassle to have to run that command every time I launch the app on the simulator. Previously the permissions were available to change for kepler simulator, so this seems like a step back to me. It used to be that setting the timezone once on the simulator would set it permanently (at least until we had to upgrade the SDK). This is the same case with real hardware, we can change the timezone and it will remain set, so not sure I understand why this is a limitation for the simulator.
I would hope you guys consider changing it to bring it back in line with what was possible for the kepler simulator, cause it doesn’t really make sense to me that there would be limiting permissions set on something I’m running on my own machine anyway.
vega device run-cmd -c "export TZ=America/New_York && vega device launch-app -a com.fubo_development.firetv.screen.main -d VirtualDevice"
Vega operation FAILED due to an irrecoverable error: Failed: /bin/sh: vega: command not found
Additional logs can be found at /Users/chrisspadanuta/vega/sdk/vega-sdk/main/0.22.5875/logs
In the logs:
2026-01-27 14:48:50 error [DeviceManagerHandler]: Shell command failed: export TZ=America/New_York && vega device launch-app -a com.fubo_development.firetv.screen.main -d VirtualDevice
Error: /bin/sh: vega: command not found
I can run the vega command just fine from the terminal, so there’s something about running vega in the way you specified that does not work:
vega --version
Active SDK Version: 0.22.5875
Vega CLI Version: 1.2.16
Thank you for your patience and for bringing this to our attention. I’ve reviewed your reports and identified a typo in the command. My apologies for the confusion.
The correct command is: vega device run-cmd -c “export TZ=America/New_York” && vega device launch-app -a com.fubo_development.firetv.screen.main -d VirtualDevice
Please let us know if you encounter any further issues. We appreciate your feedback regarding the timezone setting mechanism and recognize the current gap in the experience. I’ve shared your feedback with the team for internal discussion as we evaluate potential improvements to the developer workflow.
Vega operation FAILED due to an irrecoverable error: Failed: /bin/sh: “export: command not found
Additional logs can be found at /Users/chrisspadanuta/vega/sdk/vega-sdk/main/0.22.5875/logs
The key detail is that run-cmd executes inside the VVD shell. So your-app-launch-command should be a device command like vlcm, not a Vega CLI command (vega device launch-app). Everything must run in the same session for TZ to apply.
CLI: Launch URI: pkg://com.fubo_development.firetv.screen.main
Mon Mar 2 14:28:43 EST 2026
…my app still does not have the correct time. I am simply printing the time at the root level of the app using a console command:
const date = new Date()
console.log('time', date.getTimezoneOffset(), date)
…and this is what I’m getting:
time 0 "2026-03-02T19:29:00.596Z"
(for reference, it is currently 14:29 or 2:29PM here)
I’d expect getTimeZoneOffset() to return a number higher than 0 if this worked correctly (I believe it should be 240).
I even tried killing the app vega device terminate-app -a,com.fubo_development.firetv.screen.main,-d,VirtualDevice then running the command you specified again and it still does not have the correct time.
As Ivy mentioned earlier, Vega Virtual Device currently has a read only filesystem, so changing the device timezone is not available at this time. Also, the current documentation does not mention a way to set or change the timezone on VVD.
I confirmed that using export TZonly affects the shell environment. It does not carry over to the app process, which is why date in the shell can show the expected time while new Date() inside the app still returns the same time as before.
