Drafts Beta Program

Beta Warning

The beta program provides early access to new features and bug fixes in exchange for the promise you will document and report issues and give feedback to help make Drafts better. Do not join the beta program if you are not comfortable with running software that is not well tested and may have bugs and/or incomplete features that might put your data at risk.

Table of Contents

1. Beta Guidelines (Please Read)
2. Join Slack and Forums
3. Join the Drafts TestFlight(s)
4. Leaving the Beta Program
5. Changelog
   1. 39.1 (262)
   2. 39.1 (261)
   3. 39.1 (260)

---

Beta Guidelines (Please Read)

• READ RELEASE NOTES. Stay on top of changes, and please test new and changed behaviors.
• An active Drafts Pro subscription is required to use Drafts betas.
• Submit Feedback via the methods below. These methods will automatically include information about the app version, etc., that are helpful for troubleshooting.
  • iOS: Use the Send Feedback link in Drafts Settings, or via the Send Beta Feedback option in Apple’s TestFlight app.
  • macOS: Select Help > Send Feedback in Drafts.
• Check for Updates. When new versions are in active development, new builds come out frequently.
• If using a beta on one platform, use it on all platforms.
• Backup Often! Enable Drafts periodic backup features.
• BETA Reset: We periodically remove all beta testers from TestFlight. You may need to sign up again after one of these purges.

Join Slack and Forums

• Signup for the Agile Tortoise Slack Workspace. Discussion and announcements specific to beta builds and features are conducted in this Slack.
• Signup for Community Forum Account. If you do not already have an account on the Drafts Community Forum, please sign up. Important notices will be sent through the site – although it is generally preferred that beta-related discussions take place in the Slack.

Join the Drafts TestFlight(s)

Drafts betas are distributed using Apple’s TestFlight. To join the beta:

• Download TestFlight. You will need TestFlight installed on any iOS or Mac devices you plan to use the beta.
• Request TestFlight Access. You will need to request access separately for iOS and macOS via the links below:
  • Join iOS TestFlight
  • Join macOS TestFlight
• Follow TestFlight instructions to install builds via TestFlight app.

Please read updates notes for new version as they are released in the TestFlight app, or on the changelog below.

Only a limited number of spots are available in TestFlight! If you are unable to join, check back in a few weeks and we may have made additional slots available.

Leaving the Beta Program

In general, if you no longer wish to participate in the beta, the App Store versions of Drafts can be re-installed by downloading them from the App Store directly over the beta version.

Changelog

Covers only changes since last App Store releases.

39.1 (262)

• draft.linesWithPrefix(prefix) [string] convenience method to return only lines starting with a certain prefix string in the draft.
• Mail action step supports additional “Reply-To” field to override the Reply-To header when sending background email.
• replyToRecipients [string] property to Mail script object. Allows optional reply to values to be set on background email.
• When sorting tags, use localized compare instead of string alpha ordering.

39.1 (261)

• Rip out a bunch of old code that was no longer in use, and refactor some aspects of the main container controller on both platforms. Also refactor a number of things to be more consistent between platforms. Please report any odd behaviors around hiding/showing draft-action lists, etc.
• Refactor routing code (affecting URL schemes, Shortcuts actions, user activities, etc.) in iOS app to match Mac implementation.
• Fix: Hiding iPad keyboard bar not working properly due to a change in iPadOS.
• New: Add timeout property to HTTP script object, which takes a time interval in seconds determining how long to wait for the request to complete. Default is still 60 seconds.
• Fix: Posting tags to Medium was not working properly.

39.1 (260)

• Rewrite dictation interface on Mac to use AVCaptureDevice instead of AVAudioEngine. This allows more reliable selection of the default mic and brings the code in-line with the iOS implementation. AVAudioEngine no longer needed for backward compatibility.
• Fix: Evernote no longer likes valid hex entity references, so use named entities where possible.
• New: Add progress indicators over editor for long-running actions.

---