I am not a "proud man". I have no problem with apologizing when I make a mistake; after all, I'm only human and I expect to make mistakes.
I am sorry for the previous two bad release and embarrassed that I seem to be apologizing a lot lately!
The previous release fixed a bug simply because it was released. Prior to that release, I accidentally mistyped the version number and it included "two dots" (65.2..4 instead of 65.2.4). That tiny, fat finger mistake caused the app to crash when it was launched because one of the first things the app does is check the current version against what is available in the App Store in order to be able to alert you when a newer release is available. The “double dot” made the version number invalid.
It was purely an "amateur hour" mistake for someone with my experience. It wasn't an obvious test case because the App Store version doesn't change until a new release occurs, but had I looked more closely at that code, I would have seen the logic flaw.
After this event, I can promise you two things: (1) there will be future bugs, and (2) something like this will never occur again.
While the bug was embarrassing and stressful, my biggest "take away" from this experience was just how supportive, patient, and encouraging the RBG Player Community has become.
You folks humbled me with your support and your words of encouragement. I posted on Twitter/X, Threads, the support site (TheRiverboatGambler.com), and via text to folks who have reached out in the past using "Send Feedback”. Everyone was understanding. Others reached out via email and were equally as understanding when I explained the situation. I did receive a few reviews that weren’t “5 Stars”, but nobody punished me with bad 1 Star reviews - which may have been fair.
In this release, I've tried to put in safe guards to prevent the "bad version" issue from ever being a problem again. I've also made some other minor adjustments that should be transparent to you.
Bug Fix: Huge shoutout to Mike, who reached out about an obscure bug in Craps. Actually, it probably wasn’t all that obscure to devoted Craps Players. In essence, if an ad showed at the same time that a Loyalty Bonus was due, after the bonus was awarded, the dice disappeared from the table. This bug was a side-effect of a bigger issue that was fixed related to Loyalty Bonuses being “swallowed” in some of the games. I’m confident that the change should prevent the dice from disappearing, but there now may be a slight delay in awarding the Loyalty Bonus if an ad is shown. The delay “should” only be one additional roll. I am going to continue to work on this issue. I didn’t take time to verify, but my gut tells me the issue likely exists in all of the “dice games”. Thanks for your patience and help, Mike! I appreciate you!
I know that of people don't use social media. Personally, I'm not a fan. But if you use Twitter/X or Threads, please consider following me so I can message you in the future when bad things happen. I also have a Facebook page that I’ve not maintained but will resurrect and try to be more diligent with respect to updates.
As I’ve said repeatedly, “I’m just one guy”. I’d rather be coding than managing messaging, but when a serious bug is introduced, that role is pretty critical and I really want to be able to communicate with you quickly in a way that ensures you will get the message. Please feel free to reach out with your ideas on the best way for me to communicate when there is a major issue.
A long time supporter, Matthew, has been encouraging me for a while to become active on Discord. That is something I am going to start to focus on with Matthew. I’d love to hear your thoughts relative to whether you are familiar with that messaging platform.
Please stay safe, folks.
~Danny| submit feedback, suggestions & requests |