Tim, thank you for at least providing me a workaround. I’m not trying to be a pain, but there is NOTHING saying that the authorization doesn’t pass information in the database component. That is something that shouldn’t be omitted. There is no way to use that user authentication in any way to secure the data online and it, therefore, serves little purpose. This app is for a company and our data needs security (as I’m sure may users apps also need security to protect user info). I built the app under the understanding that I could write rules that the firebase authentication would allow me to use. Now I need to rewrite quite a bit of it to effectively use the workaround when the firebase component SHOULD function this way or have a disclaimer.
The Kodular team even created several web pages to help you get the authentication working that have been followed to the letter by several of us and those instructions do not work. So it’s not that I think it should be doing something it wasn’t supposed to to. it’s not doing what it’s supposed to be doing.
Hi Gary,
I understand that the seamless working of Firebase Authentication and Realtime Database is quintessential to the security of your app. With that in mind, I’d like to let you know we’re still trying to fix the issue over at our end. From my testing, it seems to be an issue with an outdated library we’re using, but I’m yet to confirm a fix for the same. I’ll put up any further changes in the bug tracker topic so that all of you can stay updated. We hope to have the issue fixed by the next release.
Vishwas, thank you. I’m really not trying to be a pain in the butt. I think Kodular is an amazing piece of software and could end up rivaling Android Studio as an app creation toolkit. But, with the limitations of not being able to edit the Gradle files or the libraries ourselves, we are reliant on you guys to come to the rescue and solve problems that would normally be solvable by the app developer themselves in Android Studio.
I can tell you that the work around posted earlier today does work. I spent the morning testing that out on a new project. I just am not going to have the time to rework all my firebase blocks since our busy season is upon us where I work and I’m going to be answering phones all day for the next few months. I was hoping to get an answer to this before our season started.
But I wouldn’t even know where to begin.
My app is pretty big (spent 6 months building it) and basically all of it runs through and depends on firebase.
What is the point in authentication if you can’t do anything with it?
IMO (and the opinion of all the users who asked this same question in other posts), the biggest reason you would want to authenticate a user is to control their access to information and that means setting rules. If you have to leave your database in testing mode and the data is unsecured then authentication isn’t useful.
The Kodular team has identified this as a bug and is working on a fix. We just don’t have a time line for that fix yet.
My app is used on corporate managed accounts and I have kept customer information off the database, but there is still data I want secured being used. Other developers have user data that they need to keep secure. All we are asking for is a way to do that like we are supposed to be able to.
@GaryH If you don’t mind asking, what were you actually using? Firebase authentication only or Firebase Realtime database only or both?? I didnt understand that from the above messages.
When we set up the proper rules in firebase (not read/write: true or read/write: false, but actual rules, so that users can only read and write their own data, for example) we get an auth error in our apps.
