As mentioned in title, the UrzaGatherer Android app rotates between landscape/portrait when tilted, even if the device has "Auto-rotate screen" disabled. I suspect this is just a general change that was made to web apps in some recent version of the Chrome/Chromium engine, but have not been able to find a way to disable it through browser settings. Anyway, it's pretty annoying in my case, since I often like to browse through my decks/cards when lying on my side, and this auto-rotate makes it unusable. That said, thanks to the power of browser extensions, I have found a workaround: (until a better solution is found, or the original Chromium-engine bug/change is fixed) 1) For UrzaGatherer, use an Android browser that supports extensions -- by setting that as your default browser, or using it to add a homescreen shortcut to urzagatherer.app. (I use "Kiwi Browser" personally, but Firefox should also work -- once the deck-clickability issue here is fixed anyway) 2) Install the TamperMonkey or ViolentMonkey user-scripts extension. 3) Type/paste a user-script with the following content, and enable it: // ==UserScript== // @name UrzaGatherer rotation-locker // @match https://*.urzagatherer.app/* // ==/UserScript== document.body.addEventListener("click", async ()=>{ await document.documentElement.requestFullscreen(); await screen.orientation.lock("portrait-primary"); }); Now if you close then reopen the UrzaGatherer app/page, it will have new code present that makes it so as soon as you click something in the UI, it will lock the rotation into portrait mode. While most users probably don't need this rotation-locking, I figured I would share the code above for those that do. (since it's quite annoying when the app rotates sideways when trying to use lying on one's side)

========== 1) There was an update to the UrzaGatherer android-app a couple days ago which seems to have changed the app from a "standalone app" to a "web app", apparently using the device's default-browser to serve the website. 2) In one sense this is good, because I think it means the dev can save time by not having to push frequent updates to the app through the Play Store. 3) However, it has the negative side-effect of causing an address-bar to appear at the top of the screen, which cuts away from the already small amount of screen real-estate. 4) I tried 18 browsers in total, searching for ones that lets you add UrzaGatherer as a web-app through its "Add to homescreen" function, without causing that address-bar to show up. Of those 18, I found three that let you add a homescreen-shortcut/"app" for the site without showing that address-bar. (there's possibly a couple others which were missed due to complication I discovered later [see below], but 'tis fine) Of those three browsers, there are two "types": 1) A browser which lets you add "homescreen shortcuts" to websites, but ONLY if you run the "add to homescreen" function prior to the website's "notifying the browser of its associated app" -- after that point, the browser will replace "add to homescreen" with an "install app" function (which is not what we want since that adds the address-bar). So for these sites, you need to clear the cookies/site-data (if already loaded), refresh the page, then "add to homescreen" before the site can supply its "install app" information. 2) A browser which lets you add "homescreen shortcuts" at any point, even after the site has supplied its associated "install app" information. For type 1, there are two options: Chrome, Vivaldi For type 2, there is one option: Aloha Type 2 is preferred of course, but Aloha has two drawbacks: 1) It's not a mainstream browser (so you might not want to install it). 2) It pops up a small elipsis-icon on shortcut open, lasting a few seconds (or until swiped down). So then, I actually prefer just using the regular Chrome browser -- using the procedure above (clear cookies/site-data [by clicking the "lock" icon in the address-bar], refresh page, then quickly "add to homescreen"). This quick-adding has a drawback of meaning the site's icon is not loaded yet, so the homescreen-shortcut is just a gray background with "U" on it. (though if you're using Nova Launcher, you can long-press that icon and change it back to the regular one, which is what I've done) All that said, one might think that I have gone overboard in my searching for a way to merely avoid the display of an unneeded address-bar. But it's important, and here's why: * When you have a deck open, and you are trying to filter the cards by some rules-text, that filter-box only fits on the screen when that address-bar is avoided (you also have to tilt the phone horizontally -- but that is okay); when the address-bar is there, there is literally no way to use the full-text filtering for a deck's mainboard cards (which is a function I use very regularly). ========== The above is from a message I sent to a friend, explaining how to work-around the issue of the address-bar showing in UrzaGatherer, from a recent update. As described, I have found a way to workaround the issue by using Chrome's "Add to homescreen" function rather than using the official UrzaGatherer app from the Play Store. That said, I have reposted it here... 1) In case the developer knows (or can find) some way to avoid the space-hogging address-bar. 2) In case the developer is unaware of the issue where the "advanced filter options" are only barely fitting on-screen for some phones, requiring a workaround of: switch to landscape mode, expand advanced-options, enter filter settings, flip back to vertical (so there's space to see the cards). [and even this only works when avoiding the address-bar, as described above] Not sure what the ideal solution for point 2 is here -- maybe having the "advanced options" expand-button instead show a "scrollable popup window" when it detects that there's not enough space to display the filter-options "above the cards-grid".

For some reason, in Chrome (latest version), Urza Gatherer kept loading as v9.9.7 (or whatever the latest 9.9.X version was). I tried: 1) Refreshing the page. 2) Opened dev-tools (with "Disable cache" on), and hard-refreshed the page. This temporarily solved it, but the issue returns as soon as I close the dev-tools and refresh. 3) Cleared all cached images/files in my browser, then redid steps 1-2. 4) Updated Chrome to the latest version, and completely restarted Chrome. 5) Cleared all local-storage and cookies of the site, then redid steps 1-2. 6) Manually went into the dev-tools -> application -> service workers panel, and tried updating the worker; no improvement. 7) Tried enabling the "Bypass for network" option. This worked while dev-tools was open with that option enabled, but the site reverted to 9.9.X when I closed dev-tools and refresh. 8) Tried "Updating" the service-worker, then "Unregistering" it, with "Disable cache" on, then pressed "Empty cache and hard refresh" on the refresh button. Again, worked temporarily, but the site reverted to 9.9.X as soon as I closed dev-tools and refreshed. Having a background in web-development, I was getting quite annoyed with how the service worker somehow -- apparently -- kept retrieving an old version of the site and trying to run it. I eventually decided there is probably a bug deep somewhere in either Urza Gatherer or Chrome (I suspect it's a bug in Chrome, although maybe there's some developer-side workaround that could be implemented). In the end, I did finally find a solution: 1) I installed the "Block Service Workers" extension: https://chrome.google.com/webstore/detail/block-service-workers/ceokjgeibfjfcboemhdpkdalankbmnej (https://chrome.google.com/webstore/detail/block-service-workers/ceokjgeibfjfcboemhdpkdalankbmnej) 2) I did an "Empty cache and hard refresh" of Urza (just to be sure). The extension popped up a message asking if it should allow the service-worker to be installed/used. 3) I said "No"; and yay, v10.0.X showed up as desired. 4) I did some more fiddling around to confirm the issue was actually fixed, including clearing the extension's blocking, trying more hard-refreshes, etc. 5) After that period of fiddling, I did some regular refreshes with the dev-tools closed, and *finally* the issue seems to be resolved. (the v9.0.X has not shown up again since then, thank goodness) Anyway, since I didn't see any results for this issue during a search for it on these forums, my guess is that the problem is either rare, or something most people don't notice. (EDIT: Nevermind, it happened for a friend of mine as well. See my comment on Sep-28-2023 for the details, local steps to fix, and a proposed workaround that the developer can add.) It's probably not even worth your time to investigate it. However, because of how annoying/hard-to-fix the issue was, I figured I would mention it on these forums so people in the future can find this information through search, if/when needed.

I have added some dual-faced cards to my deck. I added them under the tag "for-free-slot". (I categorize cards in my decks by "function", with the above being the category for freeform/fun cards) Later, I decided to recategorize them under the "mana-source-lands" tag. However, no matter what I do, I cannot remove the "for-free-slot" tag from those dual-faced cards! I've tried removing the tag from the front face; I've tried removing it from the back face; I've tried removing the tag from the front, then adding it to the back, then removing it from the back. In all of these cases, I am seemingly able to remove that tag -- but then as soon as I sync Urza to the cloud (eg. "upload", wait for confirmation, then "download" again), the tag I wanted gone returns somehow. (and I've tried syncing using both OneDrive and DropBox, so that's not the problem) Anyway, the two cards I'm currently having trouble with are: "Bala Ged Sanctuary (180)" and "Khalni Territory (192)" But I have had this same issue for other cards before. I have ignored it in the past, because I didn't focus on the tags that much -- but in this case it keeps distracting me because it's messing up the card-count quotas I've set for the different functions/categories. If it would help, I'd be happy to send my collection and/or deck exports to try to help debug it.