# Our first update for iOS 17 **URL:** \ **Category:** Announcement\ **Created:** [September 18, 2023, 5:08pm UTC](https://community.bear.app/t/our-first-update-for-ios-17/11706 "2023-09-18T17:08:46Z")\ **Posts on this page:** 4\ **Page:** 1
**Author:** ![david](https://dub1.discourse-cdn.com/flex013/user_avatar/community.bear.app/david/32/6_2.png) [@david](https://community.bear.app/u/david)\ **Post date:** [September 18, 2023, 5:08pm UTC](https://community.bear.app/t/our-first-update-for-ios-17/11706/1 "2023-09-18T17:08:46Z")
Good news, everyone! We have our first update ready for iOS 17 (out today) which includes improvements and fixes to make sure you can keep on writing with Apple’s new hotness. To set expectations, we don’t have any major new iOS features today; we’re still tinkering with those. However, this update includes a couple changes that a lot of users have requested since 2.0 launched. Most notably, we’ve removed the requirements of a blank line below lists. Automatic renumbering footnote has been improved, now adding new footnote in any place won’t break the existing numbered footnote links. ![IMG_3885](https://europe1.discourse-cdn.com/flex013/uploads/bear/original/2X/c/c83210aad65f60b3bb4077e0788de8f4438bb34a.gif) To brush up on all changes in Bear 2.0.11 for iOS, check out the list below. ## Bear 2.0.11 release notes ### iOS - Updated the app for iOS 17 - Apple Watch app update for watchOS 9 - Solving a glitch of the current row when entering in edit inside a note with links and images - Removing date animation in the Notes List cells when canceling the search - Fixed issue with tagcon changing and sync - Changed how the info panel works when it comes to restoring positions - Improved search restoration on app switch ### Core - Removed the mandatory empty paragraph to close lists - Fixed bug concerning the link button when the caret is next to another link with a preview - Improved the quote rendering in various contexts - Fixed issue with multiple list elements toggling - Improved sorting autocompletion for tags and wiki-links - Fixed issue with the autocomplete preference not being respected inside the editor - Fixed XCallbackURLs-related crashes when null bytes are used as parameters - Fixed issue causing tagcons to not show in the sidebar - Various localisations fixes - A couple of theme color changes ---
**Author:** ![krssno](https://dub1.discourse-cdn.com/flex013/user_avatar/community.bear.app/krssno/32/1338_2.png) [@krssno](https://community.bear.app/u/krssno)\ **Post date:** [September 18, 2023, 10:43pm UTC](https://community.bear.app/t/our-first-update-for-ios-17/11706/2 "2023-09-18T22:43:38Z")
![Bildschirm­foto 2023-09-19 um 00.41.43](https://europe1.discourse-cdn.com/flex013/uploads/bear/original/2X/c/cc050e65c60ab7c440022b8880de463681675b07.jpeg) ---
**Author:** ![flippingeo](https://avatars.discourse-cdn.com/v4/letter/f/7993a0/32.png) [@flippingeo](https://community.bear.app/u/flippingeo)\ **Post date:** [December 4, 2023, 9:13pm UTC](https://community.bear.app/t/our-first-update-for-ios-17/11706/3 "2023-12-04T21:13:06Z")
Preface - I searched the thread to find a better place for this question, but came up short. Apologies in advance if this is too “OT”. Is it still the recommendation to backup notes before installing latest dev builds? Or is it stable enough to keep my notes safe? Should I plan to install dev updates across all MacOS/iOS builds at the same time, or is it ok to stagger them? I ask because I have been using the production builds since the first full release of Bear2. I used it for both work and personal so I needed the stability of production to ensure my work notes remained intact. Now my company is cracking down on knowledge/docs to use their provided solutions. Unfortunately, this means I’ll be using MS Loop for work PKM… It is what it is. On the bright side, it forces a partition between my personal notes and work notes, which is probably better in the long run. With that shift of using Bear for everything to just personal, I’d like to get back into using the dev builds to test these new features. ---
**Author:** ![trix180](https://dub1.discourse-cdn.com/flex013/user_avatar/community.bear.app/trix180/32/588_2.png) [@trix180](https://community.bear.app/u/trix180)\ **Post date:** [December 5, 2023, 10:21am UTC](https://community.bear.app/t/our-first-update-for-ios-17/11706/4 "2023-12-05T10:21:46Z")
Yes, we still suggest to backup your notes while using the beta because, even if it’s currently stable, it’s the instrument we use for testing new features an those are usually the primary source of new bugs. > [@flippingeo](#): > > Should I plan to install dev updates across all MacOS/iOS builds at the same time, or is it ok to stagger them? This depends on the specific update but regarding 2.1 you can have beta on one device and app store version on another.