- Added full screen capability on iPad to source code viewer.
- Added more merge requests information.
- Improved French localisation (Thanks to Youri Tolstoy).
- Fixed a bug that was causing commits and merge requests not to be shown correctly.
- Added Private Token Authentication (OmniAuth, etc).
- Minor bugfixes.
- Updated the interface to support iOS 7.
- Minor bugfixes.
- Fixed a problem when connecting using self signed SSL certificates.
- Improved Chinese localization.
- Minor bugfixes.
- Fixed a problem that was preventing the source code browser to show .py files correctly.
- Fixed a problem that was preventing the source code browser to correctly display the content of subfolders.
- Fixed a problem that was preventing the source code browser to correctly show commits on a default branch which name was not “master”.
Note – If you are still experiencing problems in the source code
browser after upgrading, it is possible that the app is still holding locally some old
cached contents. In order to resolve this, please unlink the app from your current host
and login in again.
- Fixed a bug that was preventing certain files in the repository to being displayed (ex. tcl).
- Improved stability.
- Minor bugfixes.
- Fixed a bug that was preventing certain files in the repository to be displayed (ex. php).
- Fixed wrong filename when sharing a code snippet by email.
- Fixed a possible crash when signing out or unlinking the host.
- Improved stability.
- Improved memory usage.
- Minor bugfixes.
- Untrusted SSL Connection are now allowed. Read more about it.
- Fixed a possible crash when upgrading to GitLab Control Pro.
- Fixed a problem that was preventing the app to connect correctly to certain
endpoints.
Example: www.domain.com/gitlab. - Minor bugfixes.
I am aware that some users reported few problems about be able to establish an SSL connection through the app and GitLab.
GitLab Control is very strict about the safety of accutane restores a natural beauty of your skin but buy accutane and Its Easy and Safe! your data and in order to establish an SSL connection to your GitLab server you need to own a valid SSL certificate.
One of the common problem you may face is that your certificate is self signed, so GitLab Control mark it as invalid not allowing you to establish an unsafe connection.
Due to numerous requests, we have decided to be more flexible.
Since version 1.1 you will be notified when attempting to connect through SSL using a self signed certificate and you will be able to proceed at your own risk.
This has already been implemented, but I can not pull the current version 1.0.1 because it contains a very important bug fix, which needs to be available to all of you as soon as possible.
So, this new feature will be available (for everyone) probably during the next week.
Unfortunately, these are Apple timings and there is no much I can do to speed up the process, but meanwhile I can show you how it will look like ๐
Please note that this is an exception valid only for untrusted
certificates (for example a self signed one). There may be
a bunch of others errors that can cause your certificate to be invalid, but you should
be able to fix them without the need to pay for a certificate signed by a proper CA.