A little help.
Keep exploring.

SkyRise is not yet publicly released. These instructions apply to test builds and the planned launch version. It requires iOS/iPadOS 17 or later and watchOS 10 or later; some integrations require newer versions. Install the app on your iPhone and the companion on your paired Apple Watch. Allow only the permissions needed for the features you want. Vista shows elevation and local weather; Track a hike starts an activity. You can also share your current elevation without recording a hike.

You can start a hike on the Watch or, on supported paired devices, start from the phone and connect the Watch workout. Wear the Watch snugly and grant the relevant Health permissions to get available heart-rate data. Confirm that the Watch shows an active workout; wearing it alone does not guarantee heart-rate recording. Make sure both devices have the same current app build.

Barometric pressure changes, GPS noise, filtering and missing samples can affect recorded totals. A loop is not forced to net zero. Allow a fresh sensor/location reading, check the displayed uncertainty, and compare repeated outings rather than treating small changes as exact. Calibration changes the reference elevation, not the sensor’s accuracy. Hardware support varies; iPad is especially useful for reviewing progress.

Check your connection and location permission, then tap the weather retry control. An older hike keeps its captured conditions and is not updated with today’s weather. If loading repeatedly fails, open Settings → Weather diagnostics and include the displayed error in a support email. Missing weather does not prevent recording.

On each device, use the same Apple Account, enable Apple’s Health syncing and connect Apple Health in SkyRise under You → Apple Health & iCloud. Profile/preferences sync is a separate switch. Apple controls delivery timing. Repeated refreshes should not duplicate activities. Summit checklists/photos, saved weather, notes, bio and weekly goals are local extras; use optional nearby transfer for supported records. Older Watch hikes may lack the identifier required for automatic Health matching.

Search the catalog or sort by nearby summits, then add a goal. A manual completion is labeled Manually logged. GPS/elevation confirmation needs a fresh, accurate position very near the stored summit and an elevation match. You can confirm from Apple Watch while tracking a hike. Signal quality and catalog precision can prevent confirmation even when you are at the top; manual logging remains available. Stamps and completed summits stay free. Collections are curated/provisional; some silhouettes are illustrative. Mountain points do not describe a safe hiking route.

SkyRise includes offline solar-eclipse predictions for 2024–2035. Your location and the time determine whether a partial, annular or total eclipse is estimated nearby. The live sky follows that estimated phase; cloud and weather effects can obscure it. Coverage beyond 2035 is not yet included.

Record a hike during the local eclipse window with a fresh GPS fix accurate to within 35 metres. There is no minimum distance or elevation gain, and saving a route is not required. Paused, demo and quick height-change sessions do not qualify. The award records your presence during the estimated event, not whether you could see it through clouds.

Find earned keepsakes under Adventures → Eclipse awards or in the qualifying hike. Images and 10-second videos are free and do not use the complimentary video allowance. Location, route and hike statistics are optional. The illustrative video begins with the sun in place, reaches your recorded eclipse phase at seven seconds, then holds with a gentle award glow. Reduce Motion can make the export still.

Awards stay with saved SkyRise activities and can transfer with supported Watch/nearby records. Apple Health alone does not carry the eclipse award or keepsake. Predictions are approximate and are not solar-viewing safety guidance. Follow NASA’s eclipse safety advice.

Eclipse Predictions by Fred Espenak, NASA’s GSFC. About the prediction data →

Open an activity or Share my elevation, choose a design and select image or video. Use Save to Photos or the share button once it is ready. Videos are silent, 10 seconds long and 1080 × 1920. Review location, route and health controls before sharing. Reduce Motion can make an export still. Some designs require a route, heart-rate data or a selected photo.

Free includes one successful elevation-card, hike-card or recap video creation on this device. Canceled or failed creation does not use it. After success, save or share the video before closing the preview. The allowance is local to the installation and is not shared through an account. Pro unlocks unlimited elevation-card, hike-card and recap video exports. Earned summit-celebration and eclipse keepsake videos are already free and do not use this allowance.

Pro is a one-time purchase with a planned US launch price of $5.99; the purchase screen shows the actual local price. It adds unlimited summit goals and standalone readings, more journeys/goals, a journal, deeper progress analysis, premium share designs and unlimited hike/recap videos. Open the Pro screen and tap Restore Purchases using the Apple Account that bought it. A local TestFlight/development purchase is not proof of a production purchase.

Use the app’s history, activity, summit or journal controls to remove local content. Manage Apple Health workouts separately in Apple Health. Turn off optional Health or profile sync to stop that integration; existing copies remain. Previously shared files, Photos exports, backups and Apple service records need to be managed separately. Read the privacy policy for more detail.

Confirm permissions and available storage, and check both phone and Watch builds. Quick A → B measurements need the app open; supported tracked hikes have a different background lifecycle. Interrupted sessions may have gaps. Missing heart rate, steps or GPS is not a measured zero. Before reinstalling, preserve any local-only records you need. Send support the device, OS, build and steps that triggered the issue.