All Documentation

Everywhere else

Documentation Everywhere else

Audit events: kept apps

The audit catalogue's events for kept apps: kept, deployed again, shared, changed and deleted.

The audit catalogue's events for kept apps: servers a Cloud Computer keeps running behind a link that lasts, for the people their owner shares them with.

Kept apps

TypeReported byWhenDetail carries
public_site.publishedServerA public site was published, or a new version of one.siteId, slug, version, files, bytes
public_site.changedServerA public site was paused, brought back or retitled by its owner.siteId, slug, state
public_site.deletedServerA public site was deleted by its owner; its address stopped answering.siteId, slug
kept_app.createdServerA Cloud Computer began keeping an app running, on a deploy the person approved.appId, version, port
kept_app.deployedServerA new version of a kept app took over.appId, version, port
kept_app.changedServerA kept app was renamed, shared differently, taken offline or brought back.appId, fields, access, offline
kept_app.sharedServerA person was named on a kept app, or taken off it.appId, person, can
kept_app.deletedServerA kept app was deleted.appId

A public site's events are here too: published, changed and deleted.

Try on Phone

A code that opens a phone app from the Cloud Computer's development server, for one port and a few minutes; and a build of that app started on the person's own build service account.

TypeReported byWhenDetail carries
egress.phone_defaultMacA phone app's run reached an unlisted site, let through by the phone network setting.hosts, mode
instructions.cloud_defaultMacA Cloud Computer read project instruction files without asking.files
phone_build.startedMacA Cloud Computer started a build of a phone app on the person's own build service account, after they approved it on a card.kind
phone_build.apple_connectMacA Connect Apple session on the person's Cloud Computer ended: connected, failed (with the kind of failure), handed to the Terminal, or stopped. The Apple ID, password and code are never recorded.outcome, reason
phone_build.auto_sendMacA Cloud Computer sent a finished TestFlight build to App Store Connect by itself, on the yes given when the build started; or could not.outcome
phone_build.sentMacA Cloud Computer sent a finished build to the person's App Store Connect, after they approved it on a card. Nothing is submitted for App Review by this.none
cloud_computer.phone_link_startedServerThe person started Try on Phone: an address a phone can open, for one port on their Cloud Computer, for the minutes chosen. The address itself is never recorded.boxId, port, minutes
cloud_computer.phone_link_endedServerThe person ended a Try on Phone link before its time was up.boxId, port

What these do not carry

An app is named by its id, never by its link. A site is named by its address, which is public; its files are never in an event. A deploy names the version and the port, never the command or anything the command printed. A share names the person and what they may do. Who opened an app is not recorded: the app keeps a count of opens by day and nothing else. A Try on Phone event names the port and the minutes, never the address in the code. A Try on Phone event names the port and the minutes, never the address in the code. A phone build names its kind, never an account or a key; a sending names nothing.

Server: our servers saw it.

See Also

Not what you were looking for? The help centre answers one question at a time, and the support page says how to reach a person.