Hey everyone, this update is small but mighty. Despite attempts at resolving the longtime paging issue where selecting one GIF displays another, the problem still managed to persist. So in an effort to track it down once and for all, I dug deeper… all the way into the custom paging view I'd built to discover some layout timing issues. And so, this update rights this particular wrong, and hopefully puts an end to this saga. But if not, please hit me up with an email to support@gifwrapped.co, where you'll find me desperately trying to take a nap. Until next time, remember: you look nice today.

Hello everyone. I'd hoped to get this release out sooner, but somehow, life always has other plans. Good news, though… this one has some good stuff in it. - It's been a long, long, long, long, long time coming… but GIFwrapped now has its first set of Shortcuts integrations. I'm not sure I'm 100% happy with them just yet, but we'll see where they go from here. - It only took me until 2025, and MARCH at that, but the copyright dates no longer read 2023. What even was 2024, and why have static strings for things like this in the first place? - For whatever reason, Catalyst apps on macOS don't automatically remember the last active window's location or other aspects of the screen's state… which means that GIFwrapped would just re-open in the centre of the active screen each time you open it, annoying the heck out of anyone who has opinions about window placement. You know who you are. I joke, but I also put in a bunch of effort to remember the windows most recent location and sidebar width, and I'll probably add some more aspects to the mix in future updates, because I made it easy to do. - A release or two ago, I updated the mechanics of how I track file changes, and it seems like one of those changes caused changes that occur in the background to get… lost. Like with all lost things, I retraced my steps and somehow found it in the freezer. I've added a nice little workaround to ensure it checks for any changes on returning to the foreground, so we can all sleep a little better. As always, if you need to reach out and tell me about all the things that are going horribly wrong, please toss an email at support@gifwrapped.co. I do a terrible job at responding to emails, but I read them all, and try to address any issues that come up. Until next time, remember: you're not alone.

I'm trying to get more, smaller releases out the door… so I'm back, and I bring with me a tiny collection of fixes and tweaks that I've put together since the last release. - After 2024.1 got out the door, I immediately noticed that I'd get a crash on a couple devices when doing a search because a change to how I was treating search queries was causing an Equatable and Hashable mismatch. This is why you don't write custom conformances to those protocols, kids! - When cancelling a search, one expects that one can just go on living life. However, a bug was causing GIFwrapped to crash if the results hadn't come back yet, and that just wouldn't do. I fixed the issue where the section was being released unexpectedly, made sure things got cancelled appropriately, and now one can expect life to return to normal. - It seems like there was some issues with the way the IAP validation was being done on macOS… it's just slightly different enough of a process that I had to rewrite some bits to get everything working as expected. That said, it should work properly now, just in time for me to rip it all out and replace it with some sweet, sweet StoreKit 2 code. - A change I made to the 'Save to GIFwrapped' extension accidentally broke importing GIFs where the source application provides a file URL, like the Photos app. Thankfully, I got a lovely email from someone who set me straight, and now it's working as it should once more. That's it for this one! Small but meaningful. If you want to reach out, chuck an email towards support@gifwrapped.co, or hit me up at jellystyle.social/@gifwrapped if that's more your jam. Until next time, remember: don't be a turnip.

This update has been a long time coming. Aside from general life things, I've been hard at work improving many of the underpinnings of the app, some of which might be noticeable now, some not so much. Suffice to say that this work will continue, but hopefully a little more iteratively from here on out. - The time has come to disable Twitter support. It's not something I do lightly, but it has been a long time coming. As of this release, Twitter/X URLs will throw up a special error and won't even attempt to fetch or parse the relevant tweet… or whatever it's called now. If you're curious, there's more detail on my reasoning available in the User Guide. - Someone pointed out that the selected search engine isn't respected in the Messages app, so I spent a little too long rewriting a little too much code to solve that problem. Now the vast majority of preferences are stored in a way that will enable future use within extensions, and I can cross a small bug off the todo list. Definitely worth months of delay. - As it turns out, each time a new window was opened on macOS and iPadOS (yes… you can have multiple windows!), GIFwrapped would re-run a bunch of operations that only really need to be run at first launch. This is problematic in a couple of ways, so I rearranged a few things to make things only run as many times as actually needed… which is to say "once". - Swiping between pages and even sometimes opening a GIF was resulting in some crazy behaviour, and it would transition to the wrong image, sometimes even showing the right one and then replacing that with the wrong one. Turns out it was a system I use to pull updates to the image metadata to views which was crossing the streams and showing whatever came most recently. Not anymore though. Just one GIF at a time, thank you very much. - There was also some strange behaviour with resizing the preview screen, both on macOS and iPadOS. It's a numbers thing, with the complicated scrolling and scaling logic all playing a little wiggly when not exactly right. I've made some adjustments, and it seems to work much better now, which is a relief. This also helped solve some issues with tall portrait images not playing well with the scrolling behaviour of the info panel on iPhones. - I wanted to show the current state of the info screen in the navigation button, which turned out to be a deeper hole than I intended. Nevertheless, I succeeded in my mission, and you may all behold the fruits of my labour! First it's filled… then it's not… then it is again. MAGIC! - While I was doing some concurrency work in the Save to GIFwrapped extension, I stumbled across the fact that the individual GIF pages on gifs.cackhanded.net weren't saving properly, which is the fault of the underlying parser not supporting it. I dived in, made a super minor addition, and now it works exactly as expected. There's so much more going on under the hood of this release, but some of that is for another time. In the meantime, please enjoy this release, and as always… thank you for using GIFwrapped. If you need to get in touch, you can find me by emailing support@gifwrapped.co, or you can reach out to jellystyle.social/@gifwrapped. Until next time, remember to tell someone you care about how much they mean to you.

Yeah, hey, I'm back. I think I left some stuff here… do you mind checking around? Thanks. Also, while I'm here, I might as well let you know that I've fixed a little issue with the last release. - Twitter's calls to it's own API are breaking (occasionally? it's hard to tell TBH), and it surfaced an issue within GIFwrapped's parsing. The good news is that I was able to pin it down and make the new infrastructure even better as a result. That's it! Thanks for using GIFwrapped, and remember, if you need to reach out… you can toss an email at support@gifwrapped.co which will put it directly in front of my eyes. Until next time, remember: you have the power to make someone's day!

I know! Just when you were thinking "Geez, that guy who makes GIFwrapped must be taking one hell of a nap," I appear out of nowhere and bring you an update. It's just what I do. - The big news with this update is that I finally got fed up with my insanely fragile Twitter integration, so instead of doing the normal thing and fixing it, I tore the entire Search infrastructure that I built and re-did the whole thing from scratch… and this time I didn't just use a paperclip and a wad of gum. Much better. YOU'RE WELCOME. - I was also scrolling through the simulator the other day, with a bunch of thumbnails downloading from my Dropbox library… when I stumbled headlong into a UI lockup. I took a beat, dug into it a bit, and discovered that past-Jelly chose to make every access of the connected sync client one where it has to iterate through a list and verify that the client is connected, which is… bad. Good news: it's not that way any more. - At some point, the About screen's illustration started getting weirdly inset from the screen edges, so in a fit of mild annoyance, I ripped out the SwiftUI-powered List in favour of a proper compositional layout in UIKit. Future-Jelly will probably regret this move, but he can go jump in a lake… at least this one looks and works as intended. Thanks for using GIFwrapped! If you'd like to reach out and tell me secrets (only good ones please), you can do so by emailing support@gifwrapped.co. Until next time… eat your vegetables. Unless you're a carnivore.

It's been a couple of months since my last GIFwrapped release, so I dare say we're well due for an… oh look here! It's an update! What luck! - I finally (finally!) got around to tying up some loose ends in the preview screen rewrite I _mostly_ released back at the beginning of June. This improves the behaviour of the transition from the image to info, makes the scroll gesture a little more forgiving, and has the scrollbar appearing ON TOP of the image. SORCERY! - I've been meaning to give the ol' GIFwrapped icon a bit of a refresh for a while now, so I spent a couple days in Sketch getting things nice and tight. It's pretty minor, but if it helps any… there's also six entirely new alternate icons to choose from on iOS, including a pretty spiffy rainbow one. YOU'RE WELCOME. - While testing something entirely different, I stumbled on the fact that the Dropbox sync status wasn't being updated properly, and causing it to get stuck. Long story short, past-Jelly had wired things up with a didSet and then wrapped things with a lock for thread safety, but those two things weren't living well together, so one had to go. Don't worry, though… it wasn't the thread safety part, I swear. - Shortly after launching the last update, I noticed that there were situations where a download could be enqueued multiple times. Not really a big deal, except for the fact that it also meant that the app would crash. I tweaked the code to only allow it to enqueue the download one time, so that should be the end of THAT. - There were a couple of instances where, upon following a series of steps, one could cause the search drawer to appear while looking at a GIF preview, and that's not how it's supposed to work. I threw in some breakpoints, ran through a few scenarios where I knew it was getting triggered, and it should behave a little better now. Thanks for using GIFwrapped! If you'd like to reach out and tell me secrets (only good ones please), you can do so either by emailing support@gifwrapped.co or by hitting up @gifwrapped on Twitter.

There's no shortage of things to improve within GIFwrapped, and so I've been hard at work improving things (as I'm sure you know). This release in particular has some real doozies. - A mate of mine has been gently nudging me for months about an issue with downloading and displaying the preview for GIFs stored in iCloud, and because I'm a good friend… the problem has sat in my backlog waiting for me to spend time on it for months. The good news is that I finally did, so downloads from iCloud are now less likely to fail immediately after a cold launch, or when using the Messages app. Aren't I _such_ a good friend? DON'T ANSWER THAT - iCloud downloads have historically also been a source of UI lockups, particularly when a bunch are happening all at once. With this in mind, since I was in there already, I decided to refactor things to be a little less of that. Feels much better… to me at least. - Scrolling the main grid was real janky on macOS, and I never really dug into exactly why. At some point I did make some minor improvements, but nothing particularly noticeable… until I recently looked into why the memory usage was so high. Turns out both issues had the same cause: the thumbnails were e-flippin-normous. After a little tweaking of the grid scaling to reduce the overall scale, the memory usage plummeted and the grid now scrolls very nicely. You're welcome. - I've not exactly been thrilled with the Settings screens that I built out in SwiftUI, in part because of simple stuff, like the fact that the Search History screen in Settings lost its search controller because of the way that SwiftUI embeds UIViewControllers. So when a mate of mine (not the same mate for those keeping score) showed me how to have my cake and eat it too, I was so thrilled that I just had to get it in ASAP. - I've been noticing a regular issue where results from search engines fail to be decoded for one reason or another, which isn't ideal. I adjusted the parts that were failing to make 'em a little more robust (stupid APIs returning empty strings instead of nil), and they should be OK from here on out. If you have a particular bug you'd like to see fixed, you'll be super pleased to know that you can tell me all about it. Either send an email to support@gifwrapped.co or tweet @gifwrapped… or even jump on r/gifwrapped and let me know what you're thinking. In the meantime, I'll just be over here continuing to make things a little better for y'all. Until next time!

Time for another GIFwrapped release, with fixes for bugs and some minor improvements. Very, very minor. - Pretty quickly after WWDC, I started to receive messages to let me know that the app was crashing on launch for a specific subset of very eager updaters. I don't officially support future OS versions (and I'm certainly not allowed to talk about them), but what can I say? I'm a softy. - Ever since iPadOS introduced native keyboard navigation, it's been at odds with the version I built a year or five back. This is good and bad, because while I'm definitely keen to delete code, I'm not in a position to do so juuuust yet. In the meantime, I've done what I can to improve things a touch, just to make it usable again. - The "Get Info" option in the context menu isn't really used that often, so it should be no surprise that it got broken on iPadOS and macOS somewhere along the way to updating the preview screen. A little rearranging of the logic to have the UI state updated at the right moment, and the option works once again. - The advanced command words (which start with a bang and allow you to use an alternate search engine for a query) weren't working correctly because, for whatever reason, they were getting left in the query being sent to the server, and it'd totally bone the results you got back. I reworked the way it's handled, and now they work again. Clockwork. - I wanted a better solution for my logging and analytics infrastructure that would let me share most of it between a bunch of my various apps with minimal effort. To do so, I ripped most of the good stuff out of GIFwrapped and into a format I could share, then reintegrated the whole thing back in. Not a big deal for you, but a decent quality of life improvement for me. Thanks so much for using GIFwrapped! I really hope you enjoy it, and if you don't… I guess you could probably reach out to me and let me know why? Emailing support@gifwrapped.co or tweeting @gifwrapped should get your words in front of my face, and from there I will do what I can to help.

I'm back, and it's been a hectic week… at least in part because I've been cobbling together fixes for the highest priority issues to come out of the latest release. In all honesty, this is why big releases that take a long time are dangerous: stuff slips through the cracks. If you got caught up in the nonsense, then please know: I'm truly sorry. - In moving the library state over to using Codable structures, I forgot to account for dates as being a type of thing that needed to be decoded. I know, right? This obviously came back to bite me when a bunch of people who use Dropbox or iCloud sync updated to find their local library empty, which was simply because the data couldn't be read from disk correctly. Not… ideal. - Dropbox's short-lived tokens are the gift that keeps on giving. The token update did help to ease a lot of issues—because the token could actually refresh—but there were still some calls that would occur after expiration, so they'd error out until the refresh occurred. I've now made it so that the token is pre-emptively refreshed for all Dropbox API calls, so there'll be significantly less of that nonsense. - A small difference in padding between vertically and horizontally stacked labels in the GIF Info panel was causing constant layout updates and—in some cases—causing the app to completely lock up when opening a GIF's preview. Once I tracked it down, it wasn't hard to resolve: just make certain calculations use the intended value rather than the current one. Very obvious… in retrospect. - I'm never against introducing a small engine to GIFwrapped, especially when a website's creator uses and enjoys the app. So this release adds a bonus: rudimentary support for parsing the pages of @cackhanded's prolific GIF website, https://gif.cackhanded.net. Plug in a URL (or use the share extension) and you're off. Thank me later (or more aptly, thank Mark Norman Francis, whose collection is… extensive). Thanks for using GIFwrapped! If you need assistance, are still hitting bugs, or just want to share the love, please feel free to reach out to me via @gifwrapped on Twitter, or support@gifwrapped.co if you prefer all things email. I'm here to help where I can, or at least take notes so I can make my updates better. Until next time, remember: a GIF is worth a thousand JPEGs.

Well, hello there. It's been a while! I, uh… *checks notes* …have a release for you? It's a good one, I promise. - The preview screen has seen a number of improvements and rewrites in this release, like the introduction of a new inspector for the info view on iPadOS, subtle accessibility tweaks, and the death of a solid number of very minor bugs. It's been a big task, pulling apart the absolute nonsense that existed before and weaving it back into something infinitely more stable and maintainable, but if you're keen to know what I've been doing for six months… it's avoiding this. - It's no secret that I've been wanting to find a solid alternative to Firebase, and while it's not easy to find something that is financially feasible, the upcoming GIFwrapped for macOS release forced my hand, because Firebase Analytics doesn't work on Mac Catalyst. As such, this update replaces Firebase with Bugsnag for capturing crashes, and TelemetryDeck for analytics. - GIFwrapped has had a custom search bar implementation for the search card (on iPhone and split screen iPad) for a long while, but I needed to replace it with the system version for… REASONS. Which I did. It's also not eye-burning white any more, so there's that. - For a long while, the main grid view of GIFs has been missing the tiny, single pixel high separator between each of its rows. This always bothered me, but clearly not enough to be able to add it as an issue in my bug tracker. UNTIL NOW MUAHAHAHAHA - I'm attempting to right some wrongs that I made years ago with GIFwrapped's library storage by actually using a database (don't @ me)… but it's a big, long process. Step one: improve the data structures so they can be properly replicated in a database, which I've started to do by using Codable structures instead of the serialised, wild-west dictionaries of the past. Yee haw! - On occasion, the library could get stuck in a loop where reading from the on-disk store would cause it to write to disk, which would trigger a read from disk, and so forth. This could also very occasionally mean that actual changes got lost in the process, so I found a really rudimentary way to stop reads from directly triggering writes that I'm pretty sure future-Jelly will truly hate. At least it works. Bad for him, good for you! - It was recently brought to my attention that Dropbox wasn't staying connected between launches, and to my dismay, I discovered the reason was because Dropbox switched to short-lived tokens back in… September 2021. Oops. I dug in and rewrote my authentication layer to deal with that, then updated GIFwrapped to be able to refresh the token as needed. That should be enough to allow me to forget all about this for another couple of years. - The search card was behaving a little oddly after holding a GIF for a preview when the search bar was focused. If you then cancelled out of the preview, it'd reset the keyboard, but the drawer would end up with an extra offset. It's because there's multiple notifications being fired, so I throttled that business to just react to the important one (the most recent). Thanks for using GIFwrapped! If you need to reach out, you can pop an email off to support@gifwrapped.co or hit me up via @gifwrapped on Twitter. I'm here to help, or at least to listen to what you have to say. Until next time, remember to be kind to yourself (and to those around you).

Here comes a new update to take care of some pernicious little bugs that cropped up in the last release. Nothing huge, but important nevertheless. - The recent update had a minor code change that made it so that sharing GIFs, even successfully, always resulted in a non-specific error message being displayed. Innocuous as that is, I couldn't let it stand, so I reversed the change that caused it. Did I cause another bug to spawn in the depths of GIFwrapped? Maybe. Probably. We may never know. - It turns out that when I rewrote the Settings screens, I overlooked the Premium option for disabling the watermark added to Live and Burst photos when converting them to GIFs. I connected one up to the other, so it should respect what it’s set to once again. - Like all social networks, Twitter often make changes to their website to introduce features, fix bugs… or just tweak stuff to "improve engagement". It doesn't always affect GIFwrapped's ability to download GIFs from Twitter, but sometimes they change just the right thing, and I end up with hundreds of emails telling me how bad GIFwrapped is and "how dare you censor me" which is just so much fun. Anyway, here's an update that restores parsing tweets for GIFs. Thanks again for using GIFwrapped… especially if you're a Premium subscriber! I’m hard at work getting a macOS release ready to go, but if you need to reach out, toss an email to support@gifwrapped.co, or lob a tweet to @gifwrapped on Twitter. I’ll do what I can to help. Until next time… happy holidays!

Over the past few months, I’ve been zoning in on GIFwrapped for macOS; slowly getting it ready for release, and making it as good as it possibly can be. Because it shares a large portion of its codebase with the iOS version, however, there’s a whole pile of small improvements to the iOS app that I’ve made over the past few months. Like seriously, this release of GIFwrapped almost feels like a whole new app. Almost. - GIFwrapped’s in-app settings have been getting a bit crusty of late, as apart from the occasional addition or removal, they haven’t had any love… and it was quite honestly a big ol’ mess. I’ve attempted to rectify this by taking everything and shuffling it around into more appropriate spaces, rebuilding the whole mess from the ground up, and basically just treating it like it’s important. Funny how that makes things a lot better. - A few of the list style screens got a small overhaul; like the GIF info panel and the list of files in the File Sharing folder. This effort seems to have made it all feel a little nicer, but that could just be my confirmation bias talking. Either way, it finally allowed me to rip out one of the oldest pieces of code in GIFwrapped: so long StaticTables, and thanks for all the fish. - It’s only been 18 months or so since that game about relocating to an island and paying into an untrustworthy raccoon’s pyramid scheme came out, so what better time to introduce an icon inspired by the most obvious counterpart from the game? In true fashion, you’ll have to spend a few bells on getting Premium to enjoy this icon. - The interactive swipe gesture for dismissing the preview screen could cause the screen to snap to the first GIF in its collection anytime one got cold feet and tried to cancel out; a particularly annoying bug for those Premium subscribers who have paging enabled. It’s fixed now, so let’s just chalk this up to more of those classic past-Jelly misadventures. - The GIF renaming screen’s bottom bar didn’t connect to the bottom of the screen, which looked a little weird on iPhones with safe area insets. This was due to a straight-up amateur move involving an unruly layout constraint, and has now been taken care of. - Despite my best efforts, issues causing GIFwrapped to freeze up can be incredibly tricky to track down; partly because GIFwrapped is so complex, and partly because I’m barely competent at the best of times. Nevertheless, I spent a bunch of time deciphering a handful of potential causes, tracking them down, and finally making good on clearing out what I could find and understand. - Every now and then I discover that all the objects that make up the preview screen aren’t being released properly when you exit, which causes them to stockpile in the background. This can get costly pretty quickly, and it’s not generally something you want. Anyway, it happened again, so I figured it out and resolved it… for now. - I went digging into the code for the cells within the main grid view and discovered a treasure trove of little bugs and behavioural oddities. After spending some time looking through it and tweaking things, I think I got it working just a little bit more nicely. MINOR IMPROVEMENTS FTW Thanks again for using GIFwrapped. I’m hard at work making things better and getting a macOS release ready to go, but if you need to get in touch, toss an email to support@gifwrapped.co, or reach out to @gifwrapped on Twitter. I’ll do what I can to help. Until next time, kids.

I don't know about you, but from where I'm standing, 2021 feels a bit like life is pressing the pedal to the floor. As such, it's time to make good on the, uh… threat …I made back in January: this is the last GIFwrapped release to support iOS 13. On the up side, I've spent a little time duct taping a few sore points to try and improve things before I drop it like a hot coal. - I ran across a few ways that the iCloud sync engine was causing duplicates to be created within the library. One was caused by moved or renamed files being synced from iCloud and GIFwrapped being unable to find the file locally (meaning that GIFwrapped treated it like a new file), the other being that when moving a file the update to the data store could end up happening twice. I tightened things up, found a way to better connect local copies to their iCloud counterparts, and GIFwrapped's iCloud sync should officially be the best it ever has been. - I took a dive into the screen for renaming and moving files in an attempt to make it a little smarter, a little easier to understand, and a little harder to get into a situation where one could actually break stuff in one's Library. This is predominantly just a UI refresh, and it's not perfect, but I'm hoping it'll help make moving and renaming stuff clearer. - The link on the Premium screen for managing subscriptions got broken when Apple changed it a while back, and it took me way to long to notice, and way too long for me to fix once I did (and I only did because a few nice people pointed it out to me several times, while I clearly just ignored them like a jerk? I'M SORRY, NICE PEOPLE. YOU DESERVE BETTER). - In an effort to curb the usage of App Store reviews as support requests, I've removed the link to write a review from GIFwrapped's Settings screen. You're still free to write a review—especially if you have nice things to say—but you'll have to do it the old fashioned way. Sorry! Thanks for using GIFwrapped! I'm still over here continuing to work on improving things, so if you need to get in touch, just send an email to support@gifwrapped.co, or hit up @gifwrapped on Twitter. I'll do my best to help you out. Until next time, remember: BLACK LIVES STILL MATTER.

Oh, hi there! You got here just in time for me to tell you about the improvements in this release. Nothing big, mind you; just a little touch up here and there to help GIFwrapped be the best it can be. - When I made changes to the various sharing activities in the last release, I messed up the monitoring of the underlying progress, causing it to occasionally crash on iOS 13. In my defence, KVO is finicky… but it does help to actually handle the observation stuff in the right place, which I'm definitely doing now. Promise! - In an attempt to improve GIFwrapped's handling of Twitter GIFs, I jumped in and made some small modifications to help it avoid failing before the underlying page finishes loading. This means you shouldn't be seeing errors that pop up briefly, only to be replaced with content a few moments later. It also means that the "Save to GIFwrapped" extension should finally work for Twitter GIFs again. Here's hoping it sticks for a while. - While I was poking around in the Twitter-handling code, I was able to identify a couple more potential sources of tweet content, thus improving the chances that opening a tweet URL will have a happy ending, particularly on occasions when parsing the HTML itself falls over. - On occasion, when switching from an app where the keyboard is being displayed, GIFwrapped would open up thinking that the keyboard was visible, causing it to look weird. I got a couple of bug reports about it, so I jumped in to try and stop it from happening. Fingers crossed! - The custom preview transition was a little janky for anyone using retina pixel density, so I jumped in and fixed it up real nice. While I was at it, I took a pass at making the in-app explanation of this option a little more clear, because I've gotten confused emails more than once, which is way too many. - I've had the option to disable URL sharing as a hidden debug option for a while, and in my desire to work towards a cleaner settings screen, I figured I could toss it in as an actual option. WHAT COULD GO WRONG - The settings button felt wrong being above the grid view instead of being above the sidebar on iPad, so I moved it. Yeah, you heard me. I know I promised no big changes, but I really couldn't help myself. That's it! Just a short on this time. I'm still over here continuing to work on improving things, so if you need to get in touch, just send an email to support@gifwrapped.co, or hit up @gifwrapped on Twitter. I'll do my best to help you out. Until next time!

Oh, hi there! It feels like it’s been a while. Has it been a while? I may have gotten a little caught up with all the wild new things I’m able to do by dropping support for iOS 11 and 12, but I think we’ve all made it through in one piece. Except that one person over there who appears to be… uh, three pieces? Awkward. - As of this release, support for iOS 11 and 12 has been dropped, and the plan is to move to iOS 14 only in a few months time. This is a necessary move for GIFwrapped to keep improving and expanding into the future, as it means that I can utilise more system features and… don't have to keep old, busted code around. Who's ready for some new hotness? - I wanted to try out a new bookmarks sidebar for the (eventually) upcoming macOS app, and found myself liking the concept enough that I figured I'd leave it in for iPads running iOS 14 as well. It also gave me the opportunity to upgrade the bookmarks system under-the-hood, so it means improvements for everyone (even on iOS 13)! You get improvements, and YOU get improvements! Hooray! - The GIF preview screen also got an overhaul, with everything from improvements to the (Premium) paging feature, to GIF display itself. As a bonus, Premium subscribers now get a scrub bar that allows direct manipulation of the GIF playback… it’s almost like being able to control TIME ITSELF! Almost. - iOS 14 brought with it warnings letting you know when the clipboard is accessed. In GIFwrapped, they were constantly being triggered by the presence of a couple of buttons used to make pasting from the clipboard a bunch easier, but I was able to refactor them to allow them to detect when they were necessary without actually touching the clipboard contents, so no more warnings… unless you enable the clipboard preview in settings. - If one wanted to get GIFs from a Tumblr blog, one totally could… but it wasn't exactly the best experience. You'd be limited to posts on the first page, and you'd often end up with duplicates caused by different sizes of images being embedded in the page. So I wrote a proper engine to handle Tumblr blogs. Just pop in the URL, and off you go. - I swapped out the underlying library used to create zip files within GIFwrapped (for a handful of uninteresting reasons). It’s not a perfect improvement, as the new code is slower than the old code, but everything is working smoothly, and the plans I have for this stuff can now be implemented, so I'm calling it a win. - Downloading GIFs from Twitter was sometimes blocked by an error indicating that the image was empty, i.e. no pixels. Under the hood, variable frame rates were causing the actual number of frames to be different to what I was calculating, and iOS didn't like that. By going through the frames ahead of time, I'm now able to both get the correct number of frames and also calculate the correct duration for each, so the video converts as expected. - As it turns out, if a search engine somehow returned duplicate results (i.e. the same GIF, but more than once), GIFwrapped would break down sobbing and crying on the floor, not knowing what to do. I let it know that it's OK to just ditch any duplicates, so this shouldn't happen any more. - Ever since I introduced forever-dark-like-my-soul mode to make popups and modals fit better with GIFwrapped's colour scheme, the little text field for naming new folders had black text on a very dark grey background. I fixed it, but let's all just pretend it was like that for, uh… stealth reasons, OK? Thanks for using GIFwrapped! If you discover any bugs (the software kind), and would like to see them sorted (again, the software kind… I’m not killing spiders for you), toss an email to support@gifwrapped.co, or tweet @gifwrapped. I’m listening, and I’ll do my best to help where I can. Until next time, remember: you are valid, and you are loved.

The time has finally come to deal with iOS 14, so I've done the work to make sure that GIFwrapped properly supports it. Don't get too excited: for now, it's literally a matter of "was it showing an error? GUESS I HAVE TO SUPPORT THAT", so if you were hoping with all your heart for some kind of widget or something: prepare to be very disappointed. While we’re on the topic of disappointment, let me unload a little more bad news on y’all: support for iOS 11 and 12 is going away in the very near future. In fact, I fully expect this to be the last release to support them, unless something major breaks. Now… as far as this release is concerned: - I added support for iOS 14’s limited Photos permission, so if you choose it, it should correctly show results based on what you specifically select, because that’s how the limited permission works. - The method for pulling frames from video while converting to GIF stopped working as of iOS 14; not because it's deprecated or anything, just because that sort of nonsense happens (what is life without DRAMA). Good news is that I've had a secondary option waiting in the wings, which might even be slightly faster (but is less… battle-tested), and I've activated it so that things can keep on trucking. - I was still seeing some crashes when image metadata was being updated, so I reworked some things to reduce the possibility for errors to occur, which should make the whole thing more stable… again. I call this method the stab-about-in-the-dark-until-you-hit-something form of debugging. - I’ve noticed for a while—particularly after an iOS update—that downloads from iCloud could sometimes just get stuck, and no amount of resetting or force quitting would sort things out. So I did what any sane person would, and created a custom console app to run on my iPad so that I could get some insight into what was happening, and finally managed to sort it out. - The paging feature available to Premium subscribers had a small flaw: as you paged through, GIFs wouldn't always stop animating as they went off screen, which means higher-than-expected CPU and memory use. I adjusted the way pages are loaded, only ever allowing GIFs to play when they're actually on screen, because otherwise, what's even the point? - There I was doing some spring refactoring (as you do), when I discovered that the save/sort button wasn't being updated as one might expect, meaning that the button for saving a search (a Premium feature) likely wouldn't show up when a search went through, and if it did somehow appear, it likely wouldn't leave. I hooked it up correctly, and now it should do the thing you'd actually expect it to do. - The fact that GIFs have a configurable number of loops (i.e. that it's not always infinite) is easy to miss, and as such, it's a bit of information that has been missing from the info screen for far too long. Since I need to pull that information out anyway (for the new and hopefully improved GIF playback), I figured it was high time I actually made it visible. No need to thank me or anything. - I've not run into a lot of cases where images could be discovered but not downloaded… however, in cases where the server was producing HTTP errors for an image download, the response would often be entirely misinterpreted. So I wrote an error message for every HTTP status code that exists. Easy peasy lemon squeezy. - When updating my remote configuration setup a release or two back, I managed to accidentally hardcode the wrong file as the source, which isn't exactly ideal. Wired in the right variable, and now it's like I actually know what I'm doing. WHODATHUNKIT As always, you can send an email to support@gifwrapped.co or a tweet to @gifwrapped if you’re runing into problems, or if you’d just like to share your thoughts. My ears and heart and DMs are open to hear from you. Until next time, remember: this too shall pass.

A few people noticed that the sharing menu wasn't actually doing much of anything, which is all kinds of not good. It'd show up, let you tap an option, and then pretty much disappear without so much of a "nice to see you". We had a little chat, I made some changes to the order of operations once you tap an option, and it should be much better behaved from now on. Thank you so much for using GIFwrapped! If you encounter any issues, please reach out by emailing support@gifwrapped.co, or tweet @gifwrapped. Until next time, stay frosty!

A developer’s job is never done, and I’ve been working hard to tackle as many of the issues I come across as I can, so I hope this release helps ease any problems you might be running into! - I gave the App Icon screen in GIFwrapped’s settings a little overhaul, and made some of the less exciting icons free for everyone to use. What can I say? I’m a giver. - I discovered that one of my recent bug fixes introduced a small issue that caused some values to be ignored when comparing entries before updating the library's metadata store. This is mostly fine, as any of these values would, in practice, be accompanied by others that would've been caught, but a bug is a bug is a bug, so I fixed it. - While reworking the sharing menu in the last release, I messed up some logic causing the menu's actions to be loaded up _after_ checking to see which ones had been loaded. This had the side-effect of making the share button in the preview screen fail to show the shortcut list first—which isn't how I intended it—so I fixed that. - I also did some additional refactoring of the way that share sheets (the standard iOS ones) are presented in order to enable a future feature which hasn't been switched on yet (because it isn't ready). When sharing via the standard means, you shouldn't really notice much of anything, but trust me… it’s different. - The preview image couldn't initiate a drag on the iPhone. It's absolute nonsense, I know (where are you going to drag it to?!), but that future feature might make use of it somehow, so I enabled it anyway. - I noticed that there was a fun, new crash related to the new way image metadata is updated, caused by the old copy not being removed from the store correctly before inserting the new copy. I added a fallback solution for this case (which is slower, but won't fail), and now it shouldn't be causing any more trouble. - The remote configuration setup I use to manage the minutia of certain features (like how GIFs are shared to different apps) wasn't reloading correctly when I updated the server-side file. It's not really a big deal, as the file gets bundled when shipping updates, but it's always nice when things, you know... actually work. - I was seeing an occasional crash caused by the presentation of a new-ish error alert in the Messages app. Basically it was because it being presented from a background thread, and dammit past-Jelly, you know you're not supposed to pull that nonsense. - I continue to get a lot of reports of Twitter-related issues—particularly ones where the content is considered sensitive, but the user doesn't realise it—so in an effort to reduce the number of false negatives (I'm only one guy, and not at all responsible for Twitter's life choices), I've added the ability to preview the Tweet in a browser right from the error message. - Dug into the Twitter parsing once again (groan), only to discover that a super weird bug in the library I use to pull apart HTML was bugging out on me. I'm not sure _why_, and I'm terrified to pull apart Twitter's HTML by hand to figure it out (please no), but I did manage to figure out a working solution, so now we're just gonna back up slowly. Real slowly. - I also discovered a bug that was causing some tweets to be wrongfully ignored due to a casing issue: basically, it was comparing @GIFwrapped vs. @gifwrapped and deciding that they weren't the same. That's clearly not the case, so I tweaked things to do a better job, and the results should be much improved. Thanks for using GIFwrapped: you’re a champion, probably! If you’re running into any problems with the app, please reach out by emailing support@gifwrapped.co, or tweet @gifwrapped. Until next time!

Over the past few weeks, I’ve been laying out plans for GIFwrapped’s future, so a lot of this release is in anticipation of that: rebuilding parts of the code to improve them, and to allow me to bring exciting new features to GIFwrapped down the road. Lest you get the idea that I’m a big ol’ tease, however, this release also adds something exciting and new. - Thanks to some recent refactoring of the way the main app’s universal search layer works, I was able to bundle it up and bring the feature over to the Messages app, allowing for parity between the way search works in both the main app and the Messages app. This means you can now search anywhere for a GIF to send, right from a conversation in Messages, just like you would within GIFwrapped itself. Hooray! - The code managing GIFwrapped's rather complicated share functionality—including the menus and actions that accompany it—has existed in the same form since almost the beginning (except for when I wholesale ported it to Swift), and it was getting a bit… crusty. I buckled down, tore it to pieces, and built a new version out of the rubble… which should hopefully work about the same as before. It’s really more of a self-care thing from my perspective, but at least it should be less prone to problems as I expand its feature set going forward. - Dragging GIFs from the main app’s grid view has been a thing for a while now, but I never did get around to implementing the functionality for the preview screen… until now. Just another thing to cross off my bucket list. - Thanks to a handy watch dog (woof!) that I’ve been using with my beta testers (its bark is honestly worse than its bite), I was able to surface a potential cause for the lock ups people have been experiencing: resolving bookmarks used to track iCloud files from the main thread. The moral of the story here is: don’t do that. - Tweets could occasionally be dropped from search results, particularly if they were a reply to another tweet. Fortunately, I was able to improve the quality of the results returned by tweaking how I parse replies, but I swear I will never be done fixing bugs that have cropped up thanks to Twitter's site overhaul from several weeks ago. SIGH. - I was occasionally seeing images getting stuck in an update loop, constantly attempting to merge non-existent changes back to the metadata store. Turns out the fix was two-fold: first I fixed a bug that was causing the metadata to appear to have changed even when it hadn't (oops), and the second was a little refactor to avoid modifying the store unless it's _actually_ necessary. - The preview screen wasn't handling errors particularly well, with one (rather useless) error that was used across the board. This is a regression that happened a while back, caused by past-Jelly ditching the old method of downloading and displaying images… and thus the lovely, custom errors that came with it. It's still not perfect (is anything?), but it's a damn sight better than what past-Jelly left us with. JERK. - The way I was retrieving Animated Images from Photos seems to have been broken for a while now, stopping new images from showing up in the results, but it was a fairly easy thing to resolve. I just wish I’d known sooner. - It only took me… uh… 3 years to support the fancy authentication stuff that Apple introduced back in iOS 11, but here we are. I've added it to the flow for connecting to Dropbox. That's about all I have to say about it. Thanks for using GIFwrapped, and doubly so for reading these release notes! If you’re having any trouble, please reach out by emailing support@gifwrapped.co, or tweet @gifwrapped, and I’ll do what I can to help. If you’re feeling particularly generous, a review on the App Store is always welcome, too (but fair warning: I don’t provide support through reviews). Until next time, remember: you are a large, majestic mountain trout.

Despite the (somewhat hasty) fixes for Twitter importing that went out in my last release, GIFwrapped was still having issues importing GIFs from Twitter in certain cases, so I had to go back and do some additional work on it. - The Save to GIFwrapped extension was crashing before it could parse links (like, say… Twitter links), due to the web content being loaded off of the main thread (bad developer, BAD!). I made a few changes to make sure the important calls are handled correctly, and it should be more stable now. - I was also finding that the results being returned could be… variable, based on the position of the moon, the speed of XHR requests, and which leg I was standing on at the time. I went back and tweaked the way GIFwrapped handles knowing when a page has finished loading (it'll load initial results, but then continue to update as the various XHR requests complete). It's not perfect (the in-app experience is superior because it's not under time pressure), but this has helped ensure that as many results as possible are produced. - Tweets marked as sensitive (typically because they're… naughty) used to work in GIFwrapped, but the link for the GIF got properly hidden in the recent Twitter website update, which made it not so worky. I made (significant) changes to how Twitter's site is parsed in an attempt to make a best effort to retrieve GIFs from any tweets, but if all else fails, the error should at least be more accurate as to what caused it to fail. - I still get emails from users experiencing lock-ups that I cannot detect or replicate for the life of me. Each time I do, I go into the code base and look for any possible reasons that the app could get into such a state, and then do what I can to relieve it. It hasn't worked so far, but maybe the changes I made in this release will have an effect? - Thumbnails are another source of support grief, and in this release I discovered a couple of points where the code could just… not download thumbnails. Add to that some improvements to how it handles the sheer number of downloads that can be spun up during first load, and hopefully it should be improvements all around. If you find any issues with the app, or want to send me a much-needed morale boost, tweet @gifwrapped, or email support@gifwrapped.co, and I'll get back to you as soon as I can.

There’s nothing like a string of unrelated events that take what was intended to be a smallish release focused on resolving a handful of bugs, and just blowing it out into a huge release with a bunch of additional features and enhancements. Now if you’ll excuse me, I need to collapse. - Some of you may have heard about a ginormous data-sucking monster buying Giphy, a.k.a. the search engine that powers GIFwrapped's search. In response, I feel a significant need to drop them like a hot coal, so I started by adding Gfycat and Tenor as alternatives, and then straight-up switched the default to Tenor (which is owned by Google… so only slightly better). For what it’s worth, you can still access the others: just include the bang !gfycat or !giphy with your search, and GIFwrapped'll use the respective engine for your search. - Ad networks suck for various reasons, but ads have always been a part of GIFwrapped's strategy, so I decided to swap out the big, skeezy ad network for some home-rolled code. There’s still a lot of work that’ll happen with these behind the scenes, but my aim is to have a variety of ads that honor your privacy and supports independent creators. - As if I needed more to do, Twitter went and updated their website in such a way that it broke my ability to parse tweets in search of their sweet GIFs. Anyway, solving this was two-fold: websites are now loaded using a hidden WKWebView so that any javascript can run as desired, and then my tweet parser should now also handle the updated markup. - I've had a decent number of emails and tweets telling me that the app would lock up during saving, deleting, or practically any situation where the library contents are being modified. This is a really tricky issue to solve, especially when I can't replicate it on my end, but I took a dive into my threading and locking code to try and alleviate any potential pain points I could find. Fingers crossed, I guess? - When using Dropbox, library changes weren't properly getting pushed to the server unless an image was accessed or modified, which is sorta weird, and not entirely desirable. It should now make an attempt when sync is first started up, just in case. - In other Dropbox news, the library wouldn't get cleared out properly when disconnecting, likely due to some incredibly minor change that happened months ago and flew under the radar. Love it or hate it, this is the intended behaviour, so I went in and fixed it up. Please throw your tomatoes one at a time. - Fun fact: the main UI actually has two separate search bars that are kept in sync. One lives in the "drawer", and the other is popped into and out of the navigation bar as needed on iPad. Problem is, they could get into scraps over whose job it was to perform a search, causing a crash. Here's hoping they play nice going forward. - Malformed paths were still a thing that I was seeing errors for, and it turns out that, while implementing my "fix", I fell for the same ambiguity that caused the issue in the first place. Good news is that I was able to fix it properly this time, and I also took a moment to clear up the ambiguous code, to avoid this sort of nonsense happening again. - The preview transition where the image grows out of the grid view was a little… wobbly, and showing a few cracks here and there. So I took a closer look, and fixed a few small details that add up to a much smoother transition that uses significantly less memory. You're welcome. - Thumbnails got a a little lovin' as I delved in and refactored the system that manages their creation and storage to make it easier for me to follow, and thus work better. I also made it a nice coffee, so it should hopefully be less likely to jam up or drop images now. If you come across any issues with the app, I’m here to help… or at least listen, and then disappear while I head off to try and resolve them. Tweet @gifwrapped, or email support@gifwrapped.co, and I'll get back to you as soon as I can.

I’m back yet again, and attempting to resolve a number of problems that have been bothering people… and also some that weren’t. - I doubled the number of alternative app icons available to Premium subscribers, mostly by adding a bunch of colour variations. There’s also a new screen that shows up in the Settings screen (again… for Premium subscribers), making the option a little easier to find. - I (finally) added a full Search History list to Settings for Premium subscribers, with all the sweet functionality you'd expect. That should make it a little easier to manage. - Keyboard shortcuts for the preview screen stopped working at some point, so I jumped in and wired them up again, adding some new ones to support the new paging feature while I was at it. What can I say? I'm a giver. - Normally my philosophy is "I don't support iOS betas", but I was seeing a truckload of pointer-related crashes from people continuing to use early iOS 13.4 betas, even after it was officially released… and couldn't escape the emails/tweets. So I fixed it. Please update your dang phones. - A previously-resolved bug seemed to have let some "malformed" names through when renaming entries, and despite resolving the issue itself, there were a handful of sync issues that resulted from these bad paths. I added some workarounds to help resolve these, so hopefully it should all balance out now. - I've had one user in particular who has been struggling with a crash on launch that has been real hard to nail down. I went through my crash list, identifying and resolving a bunch of crashes… but knowing my luck, they’ll still have problems. I'm doing my best, promise! If you spot any problems with the app, please be sure to let me know. Tweet @gifwrapped, or email support@gifwrapped.co, and I’ll be sure to take note. Don’t forget to wash your hands!

Back again! Had a couple of tricky bugs to figure out this time around, and took the opportunity to add some of that sweet, sweet pointer action that you can do on iPad now. - Took a pass at the low-hanging fruit around hover gestures on iPad, mostly hitting the spots that already had arrow key support (plus a couple of extra spots where it made sense). I'm sure there's more that can be done, but it's a great start. - A few people (more and more) have been seeing a crash on launch which I just couldn't get enough information on to properly fix. Managed to sort the information part out in the last release, which allowed me to nail down a potential cause and resolve it. I'm basically a detective now. - Chonky GIFs are and always will be problematic for me (due to their extra-cuddly size), and most recently they were blocking the UI for a moment when loading, which became real apparent when swiping through previews. One of the heaviest parts of loading a GIF is decoding the data, which the library I use does on the main thread (where UI stuff is done), so I moved that to a background thread and it feels muuuuuuch smoother now. Until next time. Stay safe out there!

Small update this time around, to attempt a quick turnaround on a couple of bugs that were causing people headaches. Sorry about that, y'all! - To get the preview transition animation right, the two screens involved compare notes on where the image comes from. If paging is disabled (like because it's a premium feature, and not everyone has Premium?), the two views can have _very_ different ideas, and this caused significant problems. I helped the two calm down and talk to each other, so it should be ok… for now. - I'd made some last minute changes to the diffing used for the bookmarks view (it was custom, and I wanted to rip it out in favour of DifferenceKit, yes I know iOS 13 has it built in, get off my back MUM), and it made it so that clearing the clipboard would mess up the updates and crash. Anyway, it's fixed now, go team! Hope you've been washing your hands. Until next time!