Welcome aboard! I can’t wait to see what you think.

First of all, join us on the Slack group, where most discussion happens:

You’ll find the #beta channel on the Slack once you join – that’s the best place to get in touch about the beta.

If you get a crash, you’ll be prompted to describe what you were doing. Please fill that in. I also really appreciate follow-up messages with more detail. Try to figure out the situation that brought it about, and see if you can reproduce the crash. I adore a reproducible crash report! Although crash logs tell some of the story, it’s often not much, and part of being a beta tester is helping to figure out the rest.

Before making any feature requests, do check the roadmap; it may already be in there.

See you on the Slack!

Reporting Issues

Getting in Touch

Please use the Loopy Pro Beta Slack to report issues, ask questions and discuss features. At a pinch, you can email me at [email protected].

Please do not try to report issues via the Audiobus forum, as I’m not checking it. I’m also only infrequently checking the Loopy forum at present, as the Slack group seems to be working much better for this stage.

When reporting issues, please provide as much detail as you can. The goal here is to help me to understand how the issue comes about, and ideally how to reproduce it, so the more info, the better!

A reproducible issue report makes me a very happy and grateful developer 😉

Reporting Crashes

Again, the main aim here generally is to help me figure out how to reproduce a problem, so I can investigate.

TestFlight has a built-in crash reporter which appears immediately after a crash occurs. Please fill in as much detail as you can here, as it helps me figure out how to reproduce the crash. If you’re in a hurry, feel free to just add a quick note in here, and then send the rest via an email later – feel free also to record a quick voice message describing what happened, and email that, if it’s easier.

After the crash happens, while it’s fresh in your mind, please see if you can reproduce it, by going through the same steps. Loopy should routinely auto-save your project, so hopefully most of it will still be there. If you can reproduce the issue – fantastic! – then please do send me your Loopy project (using the “Export” function), unless the crash can be reproduced on a clean project.

If you’re getting crashes on launch (Now we’re talking! Just the kind of thing we want to catch and fix!), then I’d love to see your Workspace.lpproj. Open the Files app, then navigate to On My iPad, then Loopy, and find Workspace.lproj, long press on it, then tap Share and email it to me ([email protected]). Then delete or rename it so that you can launch Loopy again.