Do you develop on Windows or Linux and only need a Mac to archive, sign, and upload your app? Tell us which framework you use, your preferred region, and how many days you need a Mac. We’ll help you plan the setup. For connection, payment, or billing issues with an existing order, submit a ticket in the console so everything stays with the same order record.
We offer two contact channels: support email and console tickets. The form below creates an email draft; it does not send a message.
Tell us whether your project uses Flutter, React Native, Unity, or another framework, and whether you need a simulator, multiple projects running at once, or extra storage. We’ll recommend a setup based on your workload, but can’t guarantee a fixed build time.
Get plan adviceFor connection problems, a slow desktop, payment checks, or billing questions, start with our support guide. If you still need help, sign in to the console and open a ticket with your order number and region.
Troubleshooting guideInclude the number of people releasing at the same time, how many days each person needs, your project types, and their connection regions. Each machine has its own rental record—don’t put multiple people’s workloads on one shared machine.
Plan team accessShare your goals, preferred regions, expected number of machines, and timeline. Business and technical enquiries go to the same support email, so there’s no need to look for a separate contact.
Email about a partnershipUse the fields below to organise a plan enquiry, team rental, or partnership request. Review the draft, then send it from your own email account to support@testmini.com. This page does not upload your entries; your email app sends the message.
Team rentals are based on dedicated physical machines. Each machine is used by its assigned renter and is not a virtual machine. Team members can choose different regions based on where they connect from; the whole team doesn’t have to use the same one.
If two team members need to use macOS at the same time, plan for a separate machine for each. If one person is working through several projects in turn, first check whether their memory, storage, and parallel-tool needs call for an additional machine.
When you enquire, include: concurrent users and each person’s project type.
A one-day archive and several days of ongoing testing are different needs. Choose a daily, weekly, monthly, or quarterly period for each machine. Don’t add everyone’s rental days together and treat the total as one machine’s rental period.
When you enquire, include: each machine’s start and end dates, and time zone.
Orders and bills are listed separately for each machine. You’ll need to arrange transfers of projects, dependencies, and build outputs between regions; adding a machine in another region doesn’t automatically sync data from your existing machine.
When you enquire, include: team members’ regions, preferred locations, and data transfer needs.
An email enquiry helps us understand your needs; it doesn’t place an order or reserve a configuration. Check the console for current machine options, rental periods, add-ons, and availability. Don’t use an estimate from an enquiry email as your final bill before confirming the details.
Personal rentals, team rentals, and partnership enquiries follow the same payment terms. You can tell us which payment method you prefer, but availability depends on the payment gateway response. Email replies don’t replace the payment details shown at checkout.
Use the payment details shown at checkout and check the network, amount, and payment requirements. If you need help verifying a payment, include your order number and transaction hash in a console ticket. Never share your wallet’s private key.
Currency: USDCard payments are processed by Stripe. If the payment result doesn’t match your order status, share your order number, the time of the attempt, and the message shown on the page. Don’t email your full card number or security code.
Currency: USDCheck the plans page for machine and rental-period details. For discrepancies with a bill that’s already been issued, follow up in a console ticket to keep your order history in one place.
Enquiries are generally handled during Asia-Pacific business hours. Include a time zone with dates so “release today” is clear to everyone. Our regions operate 365 days a year, but that doesn’t mean enquiries receive an immediate reply.
We handle plan advice, team arrangements, and partnership enquiries based on their content. We don’t promise a fixed response time in hours. Reply to the original email thread with any additional details. If your release has a firm deadline, mention it in your first email.
Submit tickets in the console for connection, payment, billing, or machine issues. Response times and progress are provided in the ticket; immediate handling isn’t guaranteed. Add screenshots, logs, or new details to the existing ticket instead of opening another for the same issue.
Include the date, time, and time zone when the issue occurred, and whether you can still reproduce it. For connection issues, include your connection region, selected region, and browser. For build issues, include tool versions, the steps that failed, and an error excerpt with sensitive details removed.
Support covers connection, remote desktop, environment setup, and billing issues. We don’t write application code or manage signing credentials. While you wait for a reply, use the support guide to check your connection and toolchain.
Sign in to the console and open a ticket linked to your order. Include the region and when the issue occurred. If you haven’t ordered yet and know which setup you need, you can start renting now.