mirror of
https://github.com/Swiftgram/Telegram-iOS.git
synced 2025-12-16 03:09:56 +00:00
Update changelog and some documentation fixes
This commit is contained in:
parent
49e99fb884
commit
9c0427d392
@ -1,3 +1,54 @@
|
||||
## Version 3.1.0 Beta 1
|
||||
|
||||
- General
|
||||
|
||||
- [NEW] Added support for iOS 7
|
||||
- [NEW] Added support for arm64 architecture
|
||||
- [NEW] Added `BITStoreUpdateManager` for alerting the user of available App Store updates (disabled by default)
|
||||
- [NEW] Added `BITAuthenticator` class for authorizing installations (Ad-Hoc/Enterprise builds only!)
|
||||
- [NEW] Added possibility to build custom frameworks including/excluding specific modules from the static library (see `HockeySDKFeatureConfig.h`)
|
||||
- [UPDATE] User related data is now stored in the keychain instead of property files
|
||||
- [UPDATE] SDK documentation improvements
|
||||
- [BUGFIX] Fixed multiple compiler warnings
|
||||
- [BUGFIX] Fixed a few UI glitches, e.g. adjusting status bar style
|
||||
<br /><br/>
|
||||
|
||||
- Crash Reporting
|
||||
|
||||
- [NEW] Integrated PLCrashReporter 1.2 beta 1
|
||||
- [NEW] Added optional support for Mach exceptions
|
||||
- [NEW] Experimental support for arm64 (will be tested and improved once devices are available)
|
||||
- [UPDATE] PLCrashReporter build with `BIT` namespace to avoid collisions
|
||||
- [UPDATE] Crash reporting is automatically disabled when the app is invoked with the debugger!
|
||||
<br /><br/>
|
||||
|
||||
- Feedback
|
||||
|
||||
-[NEW] New protocol to inform about incoming feedback messages, see `BITFeedbackManagerDelegate`
|
||||
- [UPDATE] Added method in `BITFeedbackComposeViewControllerDelegate` to let the app know if the user submitted a new message or cancelled it
|
||||
<br /><br/>
|
||||
|
||||
- App Store Updates
|
||||
|
||||
- [NEW] Inform user when a new version is available in the App Store
|
||||
<br /><br/>
|
||||
|
||||
- Ad-Hoc/Enterprise Updates / Authentication
|
||||
|
||||
- [UPDATE] Removed delegate for getting the UDID, please migrate to the new `BITAuthenticator`
|
||||
- [NEW] `BITAuthenticator` identifies app installations, automatically disabled in App Store environments
|
||||
- [NEW] `BITAuthenticator` can identify the user through:
|
||||
- The email address of his/her HockeyApp account
|
||||
- Login with his/her HockeyApp account (does not work with Facebook accounts!)
|
||||
- Installation of the HockeyApp web-clip to provide the UDID (requires the app to handle URL callbacks)
|
||||
- [NEW] `BITAuthenticator` can require the authorization:
|
||||
- Never
|
||||
- Optionally, i.e. the user can skip the dialog
|
||||
- On first app version launch
|
||||
- Whenever the app comes into foreground (requires the device to have a working internet connection)
|
||||
<br /><br/>
|
||||
|
||||
|
||||
## Version 3.0.0
|
||||
|
||||
- General
|
||||
|
||||
@ -7,7 +7,7 @@ This is a checklist to help find the issue if crashes do not appear in HockeyApp
|
||||
|
||||
2. Check if CFBundleIdentifier in your Info.plist matches the Bundle Identifier of the app in HockeyApp. HockeyApp accepts crashes only if both the App ID and the Bundle Identifier equal their corresponding values in your plist and source code.
|
||||
|
||||
3. Unless you have set `[BITCrashManager setCrashManagerStatus:]` to `BITCrashManagerStatusAutoSubmit`: If your app crashes and you start it again, is the alert shown which asks the user to send the crash report? If not, please crash your app again, then connect the debugger and set a break point in `BITCrashManager.m`, method `startManager` to see why the alert is not shown.
|
||||
3. Unless you have set `[BITCrashManager setCrashManagerStatus:]` to `BITCrashManagerStatusAutoSend`: If your app crashes and you start it again, is the alert shown which asks the user to send the crash report? If not, please crash your app again, then connect the debugger and set a break point in `BITCrashManager.m`, method `startManager` to see why the alert is not shown.
|
||||
|
||||
4. Enable the debug logging option and check the output if the Crash Manager gets `Setup`, `Started`, returns no error message and sending the crash report to the server results in no error:
|
||||
|
||||
@ -22,7 +22,5 @@ This is a checklist to help find the issue if crashes do not appear in HockeyApp
|
||||
|
||||
8. Remove or at least disable any other exception handler or crash reporting framework.
|
||||
|
||||
9. If there an older version of PLCrashReporters framework `CrashReporter.framework` added to the project, remove it.
|
||||
|
||||
10. If it still does not work, please [contact us](http://support.hockeyapp.net/discussion/new).
|
||||
9. If it still does not work, please [contact us](http://support.hockeyapp.net/discussion/new).
|
||||
|
||||
|
||||
Loading…
x
Reference in New Issue
Block a user