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've been in touch with @RikTheVeggie but at the moment can't offer any further clues as to why it's stopped working.
It sounds like Huw and I are getting different results from the API as it's still not working for me, or maybe there's an intermittent issue which is why it looked fine when Huw tested it.
I have to run off to work unfortunately but I'll try to monitor mail etc as much as possible, and will jump back into investigations tonight if the issue continues to persist.
The server was rebooted yesterday and while that shouldn't have caused any problems I can't think of a better explanation.
Note: Actually while verifying I noticed that myBrickset says I have 292 sets owned, but Brickset.com shows 356. Do they count differently? Wondering if .com number includes duplicates while the android app only counts unique sets?
myBrickset reports on both the total number of sets owned (including multiples) and the number of unique sets - eg 824 (510 unique). These numbers should agree with what's shown on http://brickset.com/mycollection.
The piece count is different to brickset.com, this may be a bug - myBrickset might not be counting pieces for multiple counts - I'd have to investigate a bit more.
I did discover a bug when looking at the Summary details - total owned value doesn't count duplicates. So I'll fix that for the next release.
Other than that, thanks again for a great app! :-)
To be honest I'm still not keen on the implementation of that view either (and never use it myself so I tend to forget about it), but aren't sure what to do to improve it yet.
It certainly doesn't hurt that the app itself is pretty awesome too. :-) Thanks for all you do!
I've given it a thorough test but please let me know if you notice any issues.
Was working fine on my Z3...is this something to do with the https update?
Great app, keep up the good work :-)
Or does it build the list from all the themes that have ever existed on Brickset?
PS I second the thanks, probably the most used app on my phone...
@NickF22 - this list is built on the fly from brickset.com (it normalises the data into a separate table), I've never considered that it could end up with obsolete data in. I'll take a look, it should be reasonably easy to clean it up.
@RikTheVeggie, brilliant, all sorted, many thanks for the quick response and keep up the good work
@nwr122 - excellent, thanks for confirming. And welcome to the forum!
@VorpalRyu - hmm, I think you're seeing "place holder" data from before the set name was known. Sometimes the underlying id in the data that Huw provides changes, but myBrickset should be able to handle that ok. Would you mind sending me a copy of your db too so I can confirm the issue and prove that any fix I come up with resolves it?
Here you go folks, this should resolve all of the issues you reported. I never realised so much obsolete data was able to build up - using one of the sample dbs you provided, myBrickset was able to remove 264 sets, 8 themes and 250 subthemes! This cleanup is now automated and should stop the issue from occurring again in the future.
You can grab a copy here: otissoft.co.uk/mybrickset/bin/myBrickset-2.5.8.apk (4.3MB). I'll push it out to the play store in a couple of days once you've confirmed it seems to be working as expected.