Skip to content

ParseInstallation timeZone missing #701

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Closed
vanyasem opened this issue Feb 1, 2022 · 3 comments
Closed

ParseInstallation timeZone missing #701

vanyasem opened this issue Feb 1, 2022 · 3 comments
Labels
state:duplicate Duplicate of already reported issue type:bug Impaired feature or lacking behavior that is likely assumed

Comments

@vanyasem
Copy link

vanyasem commented Feb 1, 2022

As explained in #95 (and #96) currently there is no a proper way to get time zone as Parse Server expects in Flutter, one solution would be using platform specific code.

In fact #186 was merged, but then reverted. I could not find an explanation to why exactly that happened - maybe that was done by mistake.
@parse-github-assistant
Copy link

Thanks for opening this issue!

  • ❌ Please edit your post and use the provided template when creating a new issue. This helps everyone to understand your post better and asks for essential information to quicker review the issue.

@mtrezza mtrezza added the type:bug Impaired feature or lacking behavior that is likely assumed label Feb 6, 2022
@RodrigoSMarques RodrigoSMarques added type:feature New feature or improvement of existing feature and removed type:bug Impaired feature or lacking behavior that is likely assumed labels Apr 26, 2022
@mbfakourii
Copy link
Member

mbfakourii commented Dec 19, 2022 •
edited
Loading

FlutterNativeTimezone.getLocalTimezone()

It does not support Linux, Dart, and Windows, it seems not good for use in Parse kernel

It is better to find a replacement for it

This was referenced Dec 21, 2022
Merged
Merged
@mtrezza mtrezza added type:bug Impaired feature or lacking behavior that is likely assumed and removed type:feature New feature or improvement of existing feature labels Dec 22, 2022
@mtrezza
Copy link
Member

mtrezza commented Jan 16, 2023

Duplicate of #96

@mtrezza mtrezza marked this as a duplicate of #96 Jan 16, 2023
@mtrezza mtrezza closed this as completed Jan 16, 2023
@mtrezza mtrezza added the state:duplicate Duplicate of already reported issue label Jan 16, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
state:duplicate Duplicate of already reported issue type:bug Impaired feature or lacking behavior that is likely assumed
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@mtrezza @vanyasem @RodrigoSMarques @mbfakourii