mirror of https://github.com/laurent22/joplin.git
Merge branch 'master' of github.com:laurent22/joplin
commit
3aeb49b469
|
@ -185,6 +185,8 @@ Any kind of file can be attached to a note. In Markdown, links to these files ar
|
|||
|
||||
Resources that are not attached to any note will be automatically deleted after a day or two.
|
||||
|
||||
**Important:** Resources larger than 10 MB are not currently supported on mobile. They will crash the application when synchronising so it is recommended not to attach such resources at the moment. The issue is being looked at.
|
||||
|
||||
# Notifications
|
||||
|
||||
On the desktop and mobile apps, an alarm can be associated with any to-do. It will be triggered at the given time by displaying a notification. How the notification will be displayed depends on the operating system since each has a different way to handle this. Please see below for the requirements for the desktop applications:
|
||||
|
@ -294,6 +296,7 @@ Current translations:
|
|||
|
||||
# Known bugs
|
||||
|
||||
- Resources larger than 10 MB are not currently supported on mobile. They will crash the application so it is recommended not to attach such resources at the moment. The issue is being looked at.
|
||||
- Non-alphabetical characters such as Chinese or Arabic might create glitches in the terminal on Windows. This is a limitation of the current Windows console.
|
||||
- It is only possible to upload files of up to 4MB to OneDrive due to a limitation of [the API](https://docs.microsoft.com/en-gb/onedrive/developer/rest-api/api/driveitem_put_content) being currently used. There is currently no plan to support OneDrive "large file" API.
|
||||
|
||||
|
|
|
@ -19,8 +19,8 @@
|
|||
<!--
|
||||
Please read the guide first! https://github.com/laurent22/joplin/blob/master/CONTRIBUTING.md
|
||||
|
||||
Due to the number of issues and limited resources, those that have been created without searching first might be closed without an explanation.
|
||||
|
||||
If you are reporting a bug, did you try enabling debug mode? https://joplin.cozic.net/debugging/
|
||||
If so, please post any error or warning.
|
||||
|
||||
For general discussion, user support or to discuss feature requests, please post to the forum https://discourse.joplin.cozic.net/ (You can login with your GitHub account)
|
||||
-->
|
||||
|
|
|
@ -18,3 +18,31 @@ It is possible to get the apps to display or log more information that might hel
|
|||
|
||||
- In the options, enable Advanced Option
|
||||
- Open the log in the top right hand corner menu and post a screenshot of any error/warning.
|
||||
|
||||
# Low-level debugging on iOS
|
||||
|
||||
Some crashes cannot be investigated using Joplin's own tools. In that case, it can be very helpful to provide a native iOS crash report.
|
||||
|
||||
For this, please follow these instructions:
|
||||
|
||||
You can send it to this address https://raw.githubusercontent.com/laurent22/joplin/master/Assets/Adresse.png
|
||||
|
||||
https://developer.apple.com/library/content/qa/qa1747/_index.html
|
||||
|
||||
Getting Crash Logs Directly From a Device Without Xcode
|
||||
|
||||
Your users can retrieve crash reports from their device and send them to you via email by following these instructions.
|
||||
|
||||
(It is not possible to get device console logs directly from a device)
|
||||
|
||||
1) Open Settings app
|
||||
|
||||
2) Go to Privacy, then Diagnostics & Usage
|
||||
|
||||
3) Select Diagnostics & Usage Data
|
||||
|
||||
4) Locate the log for the crashed app. The logs will be named in the format: <AppName>_<DateTime>_<DeviceName>
|
||||
|
||||
5) Select the desired log. Then, using the text selection UI select the entire text of the log. Once the text is selected, tap Copy
|
||||
|
||||
6) Paste the copied text to Mail and send to an email address as desired
|
||||
|
|
Loading…
Reference in New Issue