Warning, /network/kdeconnect-ios/README.md is written in an unsupported language. File is not indexed.

0001 # The Official Repository of KDE Connect iOS
0003 **TL;DR: [Download from the App Store](https://apps.apple.com/app/kde-connect/id1580245991) on an iOS >= 14 device!**
0005 ---
0007 This project is the iOS version of the group of applications called KDE Connect, which uses the LAN network to integrate devices together. For information on KDE Connect, check out:
0009 - [The KDE Community Wiki](https://community.kde.org/KDEConnect)
0010 - [The KDE UserBase Wiki](https://userbase.kde.org/KDEConnect)
0012 If you would like to talk to the KDE Connect developers & contributors (for questions or if you would like to contribute!), please join the [KDE Connect development Telegram channel](https://t.me/joinchat/AOS6gA37orb2dZCLhqbZjg).
0014 ## Beta Testing
0016 In addition to the App Store, you can also get the public testing version of KDE Connect iOS
0017 by opening [this TestFlight link](https://testflight.apple.com/join/vxCluwBF).
0018 This version also supports running on Macs with Apple silicon.
0020 ## Known Behavior and Problems
0022 - iOS is very much designed around foreground interactions. Therefore, background “daemon-style” applications don’t really exist under conventional means, so the behavior where **KDE Connect iOS is unresponsive in the background is more or less intended**. There are technically some special categories and "hacky" methods to try to get it to run in the background, but in general, there is no intended/by-design method of keeping a "daemon-style" app running forever in the background. For more information, see [this post on the Apple Dev Forums](https://developers.apple.com/forums/thread/685525)
0023 - Notification syncing doesn't work because iOS applications can't access notifications of other apps
0025 ## Bug Reporting
0027 Please feel free to give feedback about/report bugs in the TestFlight version through:
0029 - System Settings app: you can report general information such as the number of app launches and crashes by enabling Settings > Privacy > Analytics & Improvements > Share iPhone Analytics > Share with App Developers
0030 - TestFlight's integrated screenshot feedback system: upon taking a screenshot of the app, tap "export" to see an option to send it as feedback to the developer (us)
0031 - TestFlight's integrated crash feedback system: upon app crashing, an alert will appear asking you if you would like to send the crash data along as feedback
0032 - [KDE Bugzilla](https://bugs.kde.org/enter_bug.cgi?product=kdeconnect&component=ios-application)
0034 ### Data Disclosure Notice
0036 - If you don't send ANY feedback AND have "Share with App Developers" disabled, the ONLY information that the KDE developers can access about you is the date that you've installed the TestFlight app.
0037 - Enabling "Share with App Developers" discloses general information such as the number of app launches and crashes with the KDE Connect developers.
0038 - Sending feedback through TestFlight's integrated screenshot feedback system OR TestFlight's integrated crash feedback system will disclose:
0039   - User email (if chosen to disclose)
0040   - Device model
0041   - iOS version
0042   - Battery level
0043   - Cellular carrier (if applicable)
0044   - Time zone
0045   - Architecture
0046   - Connection type (Wifi, etc.)
0047   - Free space on disk and total disk space available
0048   - Screen resolution
0049   - (For Crash feedback) stack trace leading to crash
0050 - Sending feedback through [KDE Bugzilla](https://bugs.kde.org/enter_bug.cgi?product=kdeconnect&component=ios-application) lets you manually disclose as much or as little information as you would like, but all information will have to be investigated manually.
0052 ## Contributing
0054 We keep track of tasks for KDE Connect iOS using [Phabricator](https://phabricator.kde.org/project/board/159/) and accept changes through KDE Invent GitLab [merge requests](https://invent.kde.org/network/kdeconnect-ios/-/merge_requests).
0056 Many tasks only include a high level description and could be easily misinterpreted, so we'd recommend first starting a conversation in the task you are interested in implementing with your high level plan before diving into coding. Especially since KDE Connect iOS 2021 makes heavy use of both Swift and Objective-C and needs to support multiple iOS versions, it can be a bit confusing at first, so feel free to ask the developers some questions!
0058 ### Extending to Additional Platforms
0060 - [ ] [Expand to a watchOS](https://community.kde.org/SoK/Ideas/2022#Investigate_Feasibility_of_KDE_Connect_for_watchOS) companion/standalone app?
0061 - [ ] [Expand to macOS](https://community.kde.org/GSoC/2022/Ideas#Project:_Porting_the_KDE_Connect_iOS_app_to_macOS) with catalyst/native SwiftUI?
0063 ## History of KDE Connect iOS
0065 This project is a continuation of [KDE Connect 2014](https://invent.kde.org/wxiao/kdeconnect-ios), a codebase that stemmed from the Google Summer of Code 2014 program that remained largely untouched since 2014 until getting picked up again by [Inoki](https://invent.kde.org/wxiao) in 2019, where some tweaks were added to it to support TLS.
0067 KDE Connect 2021 was started as a project for Google Summer of Code 2021 by student Lucas Wang. As of mid-August 2021, the app compiles and is able to perform all of the functionalities currently implemented (though there are likely some bugs to be found). Currently, the app is not yet ready for Release distribution as it lacks certain functionalities compared to the other KDE Connect versions that either need to be implemented or are likely unviable to implement due to iOS restrictions.
0069 If you would like to check out some other posts about KDE Connect iOS, please see:
0071 - [Lucas's blog](https://students.washington.edu/zxlwang/kde_list) contains many articles covering technical overviews of this project as well as its origin and plans for the future
0072 - [Lucas's Google Summer of Code Status Report](https://community.kde.org/GSoC/2021/StatusReports/LucasWang) is another place to view a report of this project
0074 ### Troubleshooting build
0076 If you get the error `Plug-in ended with uncaught signal: 4` whent trying to run SwiftLint as part of the build, run the following command:
0078 ```
0079 sudo xcode-select -s /Applications/Xcode.app/Contents/Developer
0080 ```