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'm currently working on a fix that should resolve the issues for some scenarios, once that's complete I'll recheck the code that handles the upgrade from 2.x to see if there's a bug that I've missed.
In the meantime, the only solution is a clean install. If you care about retaining favourites etc then you should be able to export your data as the user data is fully imported.
The "huge input boxes" etc are part of Google's new standardised Material Design look & feel, they're supposed to be more responsive to user input and include some standard patterns such as a common "clear" icon and moving the hint text out of the way when you start typing. They shouldn't really take any (or much) more space than the previous ones, but if they look really bad for you then please attach a screenshot and I'll investigate - it could be you have a resolution where things haven't worked out well.
@mr_leerman good to know, thanks and sorry for the hassle!
@VorpalRyu got your logs thanks but not seeing any errors. What happens when you attempt to change currencies? eg the app crashes, drop down box is not selectable, selection is not saved, etc? I'm going to continue investigating this, trying different OS versions in the emulator, etc.
@sid3windr that is very odd, the only way that should be possible is if the data folder isn't accessible but it's a folder "owned" by the app so should always be accessible (it's the same place I write log files). Can you try sending your logs + db please? If it works then I should be able to create the export file for you as a fallback.
I'm going to push out an update shortly that should resolve the issues with the db not being populated correctly for some users, but there may still be some similar issues remaining that I haven't been able to identify or resolve yet.
Many apologies for the instability with the beta releases, I haven't experienced any of these issues locally but am working to resolve them as fast as possible.
Everyone else.. I'm hoping the last release fixed everyone's issues with not seeing any results, but please LMK (and send logs) if they persist.
I actually regret adding "built" etc because they're custom states that aren't backed up to brickset.com. I have contemplated removing them, but they remain atm because some people use them. Adding a custom tag/label for yourself on brickset.com may be a better way to track this in the future (tho' I can't sync those to the app yet, there's no tag support in the API).
Presumably you did a clean install? That would've erased the 2.x backup db and the new 3.x db unfortunately, so there's no way to get data from the app anymore.
If you have an old backup or have previously sent me your db etc then I can most likely recover the "built" state from that if you like (tho' it obviously won't reflect any changes since that point in time).
Thanks, logs received but I haven't had time to investigate yet.
By "theme>set search result" do you mean using the "expandable list" view to group by theme? I can recreate this and will take a look at fixing it - I rewrote this area from scratch recently which is probably where the bug came from. Should be an easy fix though.
My Brickset will no longer work on my Note 9 android, unless I open brickset.com and allow it to reload. Once I close the app, I have to start all over.
Can anyone suggest what I need to do to correct this problem? I did restart my phone, but that did not help.
Any suggestions would be appreciated.
That sounds like an unusual issue.. can I confirm I'm understanding you correctly please.
1. Launch myBrickset, it doesn't work.
2. In a browser, load brickset.com. No CAPTCHA etc is seen, the website loads normally (?).
3. Launch myBrickset, it works.
4. Quit myBrickset.
5. Wait a few seconds and launch myBrickset, it doesn't work.
Can you also clarify what you mean by "no longer work"? eg, you get a white screen and cannot proceed, you see the login screen but cannot login (are any errors shown?), something else?
I'm assuming you are using the latest version from the Play Store and are not in the Beta program?
When launching myBrickset and it "doesn't work", if you're seeing a blank screen have you tried leaving it for a couple of minutes? It's possible it's updating, and by the time you've loaded brickset.com and gone back to the app the update has finished which is why this seems to resolve the issue.
Yes, I did wait quite awhile, but the page remained white.
I kept the app open, and opened brickset on google. Once I did that, the "swirl" appeared and after a short time, everything was loaded as usual. But, after I closed the my brickset app, it was back to the blank screen. I did this a number of times, but no change.
I always install the updates when they pop up.
You make it so easy for me, a total non-techie, and I really appreciate all that you do.
I am sorry to have bothered you.
My brickset does load without going to .com. Usually it loads immediately, but I timed it a couple of times, and it is now taking over 2 minutes, while my data is turned on.
I tried it with my data off, and it loaded immediately.
Thank you so much, but it appears I just need to try a little patience.
It sounds like it's trying to update your database with the latest information, this shouldn't block the app from loading but maybe it's just taking too much cpu to process the data so you can't see the login screen.
I've totally reworked the startup process in the upcoming version, so hopefully when I eventually release it publicly it'll resolve your issues properly. I'll also investigate adding the ability to suppress full database updates when using a metered connection (ie mobile data).
Now I just need to get better at not introducing new bugs all the time :D
Free support is my pleasure, the app would be nothing without people like you providing free QA :p
All of your data is nice & safe on brickset.com as usual, there's just a tiny issue with the API atm which is causing a lack of data to be returned to the app. I've asked our Friendly Neighbourhood Admin to take a look, and hopefully normal service will be resumed shortly. You may have to log out and back in to fix it, but hopefully not.
I shall post again when I have more (hopefully good) news, unless someone beats me to it because of my timezone!
If you have one, could you please side-load this and let me know if it works?
I'd like to say a heartfelt thank you to everyone that participated in the beta, and especially those that contacted me here or through other channels to report & test issues.
I know the path to get here hasn't always been smooth, so thanks for sticking through and putting up with the occasional dodgy build.
It may not look like it, but 3.x includes a whole slew of improvements - most of them are under the covers but will hopefully result in a faster and more stable experience for all.
Some major improvements included in the 3.x line are:
The downside is that myBrickset now requires Android 6.0 and up. This was released 4 years ago so hopefully I'm not alienating too many users with this change. I don't like changing the minimum requirements, but have to do so in order to use newer frameworks.
- Dramatically improved performance
- Better error handling & reporting
- Improved CAPTCHA support
- Native barcode scanner
- Material design and night mode
- Much better grid & nested list views
- Fewer 3rd party dependencies
- Using the latest Android frameworks (AndroidX / Jetpack / Firebase)
If you don't have 3.x yet, you should have it by the end of the week. I'm doing a staged rollout and am currently targeting (a random) 50% of deployments.
Thank you once again for participating in the largest ever update of myBrickset. This project would not be what it is today without all of you.
the fix for this should already be in the latest build (3.0.28) that was rolled out last night [about 04:00 GMT] :) Please LMK if you're not seeing it. Hopefully it's just taking a while for Google Play to publish it in your region.
Cards for search results were previously coloured depending on whether they were owned, wanted, both or neither, and this works fine in "day" mode. In "night" (aka "dark") mode though, the text colour becomes lighter which means it gets washed out.
What I've done for now is to stop colouring the cards, and added quantity information to the list view. It's not perfect and I want to revisit it, but at least all of the data is now visible and the colours are more applicable to "night" mode.
1. On the list for owned sets sorted according to number of sets, those above 9, eg. 10, 17 etc are now listed among the 1 sets. The sorting seems to ignore the double digit numbers?
2. Under settings Cache Size it didn't show the number, only displayed the letters "MB" so doesn't know exact size allocated.
3. The number of sets owned as shown on the icon listings is light green so cannot see clearly with the thumbnail images having white background. This is already present in previous builds, just wanted to highlight it now. Maybe can allow choosing of text colour, have a shadow effect on the text or just have a black background for the text?
1. Hmm, I you're absolutely right but I don't know why it's doing this. It'll be a nice puzzle for me to figure out :)
2. Ah, I remember this one. The new framework was in "alpha" when I started using it and it didn't support showing the value at that time.. and I forgot to go back to it when the framework was finalised. I've just done some poking in the code and have developed a fix that I'll include in the next release.
3. I'm thinking of getting rid of the numbers TBH, I don't think they provide much value - but feel free to contradict me! They've been there in the grid view for a while and I just introduced them on the list view as a quick workaround because of issues colouring the card in night view.
Any fix is complicated by the fact that images are not a uniform size, aspect ratio or colour! I'm toying with the idea of colouring the cards again, using darker colours for night view, and adding additional padding in the gridview so the card colours can be seen easily.
I'll experiment with a few different techniques and see what works..
In 2.x I was able to fill list entries with a solid colour for owned and wanted items, or a gradient item for items that were both owned & wanted. I lost the ability to do gradients in 3.x due to the new framework I'm using, so introduced a new colour to represent the 3rd state.
The colours all looked a little washed out, and also caused problems in night mode so I temporarily removed them.
I've changed the colours and also introduced some darker ones for the night mode. I'll just show the regular ones here though.
Colouring the results in the grid mode didn't really work (as images are different aspect ratios so there was no consistency in the amount of colour seen); I was never happy with it, so I've reworked it to a border style which I think looks much nicer. I'm thinking of using the border for the list & group modes too, to retain consistency (it also looks nicer when the image has a background other than white).
What do people think? Solid for lists and border for grid, always use the border, give up on being a designer and stick with coding?
One concern I've had people state over email is that the sets which are owned or wanted should stand out easily among the regular ones, does this new approach satisfy that?
The images below show the list view with filled cards (closest to 2.x behaviour, but the colours are new for 3.x), list view with outlines, grid view with outlines, and group view with outlines.
Card highlighting has been changed to borders only; the final decision on which style goes into production depends on feedback I receive.
As solid fill seems to be the consensus here (tho' a few people on email opted for borders) I'll roll out with that but will also add an option to easily switch to borders.
Grids will be borders all the time, because solid fill doesn't work (unless Brickset update all of their images to give them a transparent background!)