Please use our links: LEGO.com • Amazon
Brickset.com is a participant in the Amazon Services LLC Associates Program, the Amazon.com.ca, Inc. Associates Program and the Amazon EU Associates Programme, which are affiliate advertising programs designed to provide a means for sites to earn advertising fees by advertising and linking to Amazon.
As an Amazon Associate we earn from qualifying purchases.
I am using a Samsung galaxy 6 android version 7 if that helps.
Sorry to hear that, it's certainly not something that should be happening. All of your data is still safe on brickset.com though so don't worry:)
Can you try logging out & back in? Or quitting the app and restarting? This shouldn't be necessary, but there's no harm in trying.
If that doesn't help can you send me the logs please (main screen | menu | send logs), they'll hopefully show what's going on.
Is there an email address or somewhere I need to sent the logs too?
If that doesn't work, drop me a mail at [email protected] and I'll follow up from there.
I've had a few reports that it isn't working, so would like to find out if it's isolated to an OS version or two, or whether it's affecting everyone. It's working fine on my personal device and all of the emulators I've tried (from Android 6.0 (aka API 23 aka Marshmallow) and up).
If you look at the "Result Highlighting" setting, what does it currently show? It should show "Full" - but then it should also be working! Try changing it to any other value and then back again, that should fix the colours.
Glad to hear it's working for you :)
I'd like to ask how many people use the ACM from within myBrickset, and how useful it is. API constraints mean it's read only, which reduces a lot of the functionality IMO. And I didn't do a very good job of displaying the data either! This is an area where I think the experience is a lot better directly on brickset.com, tho' I haven't tried it on a phone sized screen.
Also, does anyone actively take advantage of myBrickset's "offline" functionality? eg being able to browse the database, or update your sets, even without an internet connection? WiFi has become a lot more prevalent since I rolled out version 1.0 many years ago, and pretty much everyone seems to have a data plan now.
I don't have any immediate plans to remove the offline functionality, but doing so would reduce a lot of the complexity present in the app (frankly this is the scariest part of the code as if I get it wrong everyone's data could quite easily become out of sync with brickset.com, or overwrite data it shouldn't).
There are no immediate plans to remove the ability to update owned status whilst offline, but even if this was done I'd still want to try and retain the ability to view the current collection. I think offline access is one of myBrickset's big "selling points" over other apps, so would only remove it if either no-one used it or it became harder to support.
ACM will be removed from the next release, as the API no longer supports it.
When launching the app, if you're logged in then it verifies that your user token from brickset.com is still valid. If there's no active internet connection then it skips this check so you can still access your collection (but may not be able to sync any changes when a connection becomes available).
It sounds like your phone is reporting there's a connection when there isn't, so the app has to wait for the connection to time out. Don't know if there's anything I can do about this, but I'll go over the code to see if the API's got any improved mechanisms for checking for a connection.
I've got a couple of minor bugs to look at (unrelated to the API changes) then I'll push out a beta release to Google Play.
If you had downloaded the Beta from the Play Store, I've pushed out a new version that reverts it back to v2.
I hope to be able to publish a new v3 release next week.
It's related the new JSON parsing library I'm using, and the optimiser being a bit too heavy handed and removing information that's needed at runtime (as the parser relies on reflection).
A user reached out to me over email about the issue and I think I have a fix now - once it's confirmed I'll push out a new Beta.
I used to have code that would allow a user to access the app via auto-login even if Brickset gave an error, so the user wouldn't be blocked if there was an API issue. It's possible this is now being a bit too lenient now there's an API with better error handling, and I need to look at tightening it back up.
This would perhaps explain how people were able to use the latest version even with the bug tho'.
I've pushed the fix out to the Play Store.
The integrity of user data is paramount and I feel awful for having such a bug slip through. I sincerely apologise for this.
If you have changed any data through myBrickset today, please double-check on brickset.com that the wanted state is set correctly.
I had `>=` rather than `=` :facepalm:. Normally it wouldn't be a problem but I had another legacy bug where I was marking the wanted state as dirty when creating a record for a new set, which made it try and needlessly send the state over the API rather than just ignore it. That's where it stumbled into the comparison bug and sent wanted=1 rather than wanted=0.
Lesson learned - more unit tests and less late night coding after work!
Trying to add a few sets through myBrickset by searching. I search the number, it brings it up, I add 1 to owned, and back out back to the search page and it seems all is well. But if I go back into it, it's missing and back to 0 owned and wanted for that set.
I've also tried adding by just searching for a theme (a couple new Dots sets my daughter wanted that I bought) and I see the list of sets. I go into one, add it, and back out to the list and I see it is green like it added it. Then I go into another set, add it, and go back out to the list and that new set is green, but the other goes back to white/not added. I go into it and it is zeroed out. So I add, go back to the list, and then notice the other is back to 0. Argh! The odd thing though is that I go to brickset.com and look, and I can see those sets have been added according to the website, so it seems to have recognized it in a way.
Also tried to just add a different set through brickset.com website and then force a sync on myBrickset. When I search for the set after that, it still is zeroed out in the app so isn't seeming to recognize the addition done that way either.
Have tried the sync button in the app and even get the "Sync Complete" toast message letting me know it "worked". I've also tried force closing the app and restarting it. Also rebooting the entire phone.
Now tried just checking the sets owned and wanted from the main screen and those are both showing 0 sets. Nothing there.
Tried logging off and back on again in case there was a weird account issue, but that seemed to work fine (no login errors), but still showing 0 of everything.
This is on a Pixel 3 with latest Android. I checked Play Store and it says there are no updates, so believe I'm running the latest version of myBrickset.
Stuff like this really worries me that it is going to sync the 0 of everything to the website and wipe out my collection someday... Time to back it up to csv again...
There are API issues atm, nothing is syncing to or from brickset.com as we've blown through the max number of allowed daily requests.
Occasionally data will be synced as you've seen, as Huw temporarily increases the limit. But this only lasts a short while before it's exceeded again.
I'm working on it with Huw atm but am limited to how much I can do as I'm meant to be at my day job! A new version has been released which will limit the number of calls each installation makes and will hopefully improve things once everyone has updated.
I'll be doing more investigations tonight after work, but that won't be for at least another 6 hours.
myBrickset will only ever send "dirty" data to brickset.com, ie data you've explicitly changed in the app.
Please let me know if you continue to experience issues.
In this case though, the API was returning "success" but not sending any data back - and the app was unable to distinguish this from a user simply not having any data.
(I'm on the beta version)
I've figured out a solution that seems to work, but now it highlights that I'm only searching for the set number (720) and not the variant (2).
There are a couple of ways I could go about supporting this.. I'll have a think and try to get something in for the next release.