Skip to content
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.

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

[Bug] float and double data types saving problem #1133

Closed
nextvern opened this issue Sep 9, 2021 · 1 comment · Fixed by firebase/firebase-cpp-sdk#709
Closed

[Bug] float and double data types saving problem #1133

nextvern opened this issue Sep 9, 2021 · 1 comment · Fixed by firebase/firebase-cpp-sdk#709

Comments

@nextvern
Copy link

nextvern commented Sep 9, 2021

[REQUIRED] Please fill in the following fields:

  • Unity editor version: 2020.3.16f
  • Firebase Unity SDK version: 8.2.0
  • Source you installed the SDK: .unitypackage
  • Problematic Firebase Component: Database
  • Other Firebase Components in use: none
  • Additional SDKs you are using: none
  • Platform you are using the Unity editor on: Mac
  • Platform you are targeting: Android
  • Scripting Runtime: IL2CPP

[REQUIRED] Please describe the issue here:

image

Steps to reproduce:

Have you been able to reproduce this issue with just the Firebase Unity quickstarts (this GitHub project)?
What's the issue repro rate? (eg 100%, 1/5 etc)

What happened? How can we make the problem occur?
This could be a description, log/console output, etc.

If you have a downloadable sample project that reproduces the bug you're reporting, you will
likely receive a faster response on your issue.

Relevant Code:

var database = FirebaseDatabase.DefaultInstance;
database.GetReference("test").SetValueAsync(0.1234567890);
@paulinon
Copy link
Contributor

Hi @nextvern,

Thanks for reporting this. I was able to replicate the issue as well.

As a workaround, you may store the values as a string for now.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants