The iPhone Wiki is no longer updated. Visit this article on The Apple Wiki for current information. |
Difference between revisions of "Radar"
Dmaster4391 (talk | contribs) (Undo revision 42558 by AppleInternaliOS (talk) 7.6 hasn't even been released to the public yet, it's still in development...) |
Ryan Kovatch (talk | contribs) (added aardvark info + another version) |
||
(4 intermediate revisions by 3 users not shown) | |||
Line 1: | Line 1: | ||
+ | __NOTOC__ |
||
− | {{float toc|left}} |
||
== Summary == |
== Summary == |
||
+ | {{Infobox software |
||
− | [[Image:Radar_Web_App.png|thumb|Radar Icon]][[Image:Radar_Bugtracking_Website.png|thumb|Radar Web App Login Screen]] |
||
+ | | name = Radar (iOS) |
||
− | Radar is Apple's internal bug reporting and tracking system. iOS URL schemes are of the form "rdar://problem/123456". |
||
+ | | title = Radar (iOS) |
||
+ | | logo = [[File:Radar.png|152px]] |
||
+ | | screenshot = [[File:Radar-Dev.png|152px]] |
||
+ | | caption = Radar's production (top) and development (bottom) iOS icons. |
||
+ | | collapsible = |
||
+ | | author = Apple Inc. |
||
+ | | developer = Apple Inc. |
||
+ | | released = |
||
+ | | discontinued = |
||
+ | | latest release version = 4.4.1 (358-g0c2b6)<br /><small>(latest ''known'' version)</small> |
||
+ | | latest release date = |
||
+ | | latest preview version = |
||
+ | | latest preview date = |
||
+ | | programming language = |
||
+ | | operating system = [[wikipedia:iOS|iOS]] |
||
+ | | platform = |
||
+ | | size = |
||
+ | | language = [[wikipedia:English language|English]] |
||
+ | | status = |
||
+ | | genre = Bug reporting |
||
+ | | license = [[wikipedia:Proprietary software|Closed source]] |
||
+ | | website = |
||
+ | }} |
||
+ | '''Radar''' is Apple's internal bug reporting and tracking system for iOS, macOS, and the web. |
||
+ | The Radar app for iOS is installed from [[Switchboard (App Store)|Switchboard]], and is widely known for its URL scheme, ''rdar://''. Navigating to rdar:// on a device without Radar installed will redirect you to Apple's outward-facing web interface, [https://bugreport.apple.com/web/ Bug Reporter], which is open to external customers (such as consumers, developers, and businesses) to report bugs in production or beta Apple products. |
||
− | There are two different methods to get Radar; the first one installs the '''RadarWeb''' webapp. Start Safari, navigate to "rdar://" (without quotes), then hit the bookmark button and "Add to Home Screen". Wait a few seconds for the favicon to appear in Springboard. Another way is to download the app from [[Switchboard (App Store)|Switchboard]], which is for iPad and iPhone. To get it on OS X you must visit http://istweb.apple.com/software/download/list.php?q=radar (You need to be on an Apple Internal Network in order to access the site). Internal firmwares also include a version of Radar. |
||
+ | The Radar app is also used to file bugs at a somewhat higher priority, and for internal products as well as external ones. In many applications, especially internal ones, Radar will enable extra bug reporting and feedback features. |
||
− | Externals (Developers, Vendors, On-Site Vendors and Independent Contractors) can access Radar via RadarWeb (https://bugreport.apple.com) with limited features while Apple Employees & Contractors can access Radar via the iOS app, Radar for OS X and RadarWeb with higher privileges. |
||
+ | |||
+ | Radar is also known for its infamous mascot, the aardvark, which was previously featured in its icon. It can also be found in Radar's iMessage sticker pack, which contains 24 stickers including: |
||
+ | * FILE A RADAR. |
||
+ | * DUPE |
||
+ | * P1 (Priority 1 - Show stopper) |
||
+ | * NTBF (Not To Be Fixed) |
||
+ | * 20 stickers of the aardvark doing various things (shrugging, running, sleeping, etc). |
||
+ | |||
+ | ==The System== |
||
+ | The Radar bug system is comprised of five stages: '''Analyze''', '''Integrate''', '''Build''', '''Verify''', and '''Close'''. |
||
+ | |||
+ | ===Analyze=== |
||
+ | Radar bugs begin with the user filing a bug in either Bug Reporter (for external products) or Radar (for internal products). The bug, often referred to as a "problem," is then given an 8-digit Problem ID and assigned to an engineer (the "assignee") to investigate. The assignee can also CC the problem to other employees that may be fit to help solve it. |
||
+ | |||
+ | After proper investigation, the problem is assigned a priority: |
||
+ | * '''P1''' - ''Show stopper'' |
||
+ | * '''P2''' - ''Expected'' |
||
+ | * '''P3''' - ''Important'' |
||
+ | * '''P4''' - ''Nice to have'' |
||
+ | |||
+ | ===Integrate=== |
||
+ | Now that all appropriate engineers have been notified of the problem, they can begin developing and integrating a solution. The problem is assigned a target build for which it must be fixed by, as well as a milestone number. |
||
+ | |||
+ | ===Build=== |
||
+ | The relevant project is in the process of being built with fixes included. |
||
+ | |||
+ | ===Verify=== |
||
+ | The problem is verified to have been solved with patches applied in the most recent build. If it is not solved, return to the Integrate stage. |
||
+ | |||
+ | ===Close=== |
||
+ | The problem is now solved, and can be closed on Radar. All users that submitted the problem, including those marked as duplicate, are notified that it has been solved. Before it is archived, a resolution is added to the problem: |
||
+ | * Software Changed |
||
+ | * Documentation Changed |
||
+ | * Hardware Changed |
||
+ | * Configuration Changed |
||
+ | * Data Changed |
||
+ | * Feature Removed |
||
+ | * Vendor Disqualified |
||
+ | * Process Changed |
||
+ | * Item Completed |
||
+ | |||
+ | In some circumstances, the problem is closed without being solved. In that case, the resolution is one of the following: |
||
+ | * Duplicate |
||
+ | * Cannot Reproduce |
||
+ | * Behaves Correctly |
||
+ | * Not To Be Fixed |
||
+ | * 3rd Party To Resolve |
||
+ | * Insufficient Information |
||
== Version History == |
== Version History == |
||
− | *2.1.3 |
+ | * 2.1.3 |
+ | * 3.10 |
||
− | *7.5 (OS X) |
||
+ | * 4.4.1 |
||
[[Category:Apple Internal Apps]] |
[[Category:Apple Internal Apps]] |
Latest revision as of 07:17, 10 March 2019
Summary
Radar's production (top) and development (bottom) iOS icons. | |
Original author(s) | Apple Inc. |
Developer(s) | Apple Inc. |
Stable release |
4.4.1 (358-g0c2b6) (latest known version) |
Operating system | iOS |
Available in | English |
Type | Bug reporting |
License | Closed source |
Radar is Apple's internal bug reporting and tracking system for iOS, macOS, and the web.
The Radar app for iOS is installed from Switchboard, and is widely known for its URL scheme, rdar://. Navigating to rdar:// on a device without Radar installed will redirect you to Apple's outward-facing web interface, Bug Reporter, which is open to external customers (such as consumers, developers, and businesses) to report bugs in production or beta Apple products.
The Radar app is also used to file bugs at a somewhat higher priority, and for internal products as well as external ones. In many applications, especially internal ones, Radar will enable extra bug reporting and feedback features.
Radar is also known for its infamous mascot, the aardvark, which was previously featured in its icon. It can also be found in Radar's iMessage sticker pack, which contains 24 stickers including:
- FILE A RADAR.
- DUPE
- P1 (Priority 1 - Show stopper)
- NTBF (Not To Be Fixed)
- 20 stickers of the aardvark doing various things (shrugging, running, sleeping, etc).
The System
The Radar bug system is comprised of five stages: Analyze, Integrate, Build, Verify, and Close.
Analyze
Radar bugs begin with the user filing a bug in either Bug Reporter (for external products) or Radar (for internal products). The bug, often referred to as a "problem," is then given an 8-digit Problem ID and assigned to an engineer (the "assignee") to investigate. The assignee can also CC the problem to other employees that may be fit to help solve it.
After proper investigation, the problem is assigned a priority:
- P1 - Show stopper
- P2 - Expected
- P3 - Important
- P4 - Nice to have
Integrate
Now that all appropriate engineers have been notified of the problem, they can begin developing and integrating a solution. The problem is assigned a target build for which it must be fixed by, as well as a milestone number.
Build
The relevant project is in the process of being built with fixes included.
Verify
The problem is verified to have been solved with patches applied in the most recent build. If it is not solved, return to the Integrate stage.
Close
The problem is now solved, and can be closed on Radar. All users that submitted the problem, including those marked as duplicate, are notified that it has been solved. Before it is archived, a resolution is added to the problem:
- Software Changed
- Documentation Changed
- Hardware Changed
- Configuration Changed
- Data Changed
- Feature Removed
- Vendor Disqualified
- Process Changed
- Item Completed
In some circumstances, the problem is closed without being solved. In that case, the resolution is one of the following:
- Duplicate
- Cannot Reproduce
- Behaves Correctly
- Not To Be Fixed
- 3rd Party To Resolve
- Insufficient Information
Version History
- 2.1.3
- 3.10
- 4.4.1