Also add minimum version of Xcode we require to compile in the instructions

https://invent.kde.org/network/kdeconnect-ios/-/merge_requests/82 implementing file streaming/chunked transfer for large files is up for review, and should fix majority of current crashes on KDE Connect iOS related to file sharing

New MR: https://invent.kde.org/network/kdeconnect-ios/-/merge_requests/76

Sorry for not getting to this earlier, looks good to me!

No. I meant the camera, microphone and gps.

In T4661#280911, @apol wrote:

First make sure to start working on one of the 3 listed. I guess it depends on which you prefer we can start looking into.

First make sure to start working on one of the 3 listed. I guess it depends on which you prefer we can start looking into.

hello, i am a recent user of kde connect. And, it's awesome and smooth experience.
i am a also who have interest in implementing this feature.
can you all tell me where i can start or which direction i should look to implement it in kde connect ?

I'd want to work on this issue. Can someone direct me to the appropriate resources? I'm pretty new to C++ coding.

I would like to propose this mapping for the percentage symbols:

An action or dialog where you would be able to copy the received file on the ios device would be greatly appreciated.

Thank you very much for the review! We launched a version that has significantly fewer number of crashes compared to earlier TestFlight builds :)

Congrats on finishing Season of KDE!

Resolved in https://invent.kde.org/network/kdeconnect-ios/-/merge_requests/54

In T15318#274491, @lucaswzx wrote:

Hello, @Guilhermems. Thanks for writing up those instructions! It's a nice, quick documentation for all the KDE Connect clients. But I would like to point up a couple of things about the iOS client in particular.

Near the end of the page, you what I assumed to be a general statement for all KDE Connect clients:

"After finishing the steps for your platform, your file will be transferred in the background to the Downloads folder of the receiving device. You can also check your device’s notifications for more information about the progress."

Regarding KDE Connect iOS, the differences are:

• • KDE Connect iOS doesn't currently have background activity support (due to iOS urge to really, REALLY want to suspend apps in the background), so in order for the file to actually download (or any part of the app to work), the app NEEDS to stay in the foreground with the device unlocked and running.
• KDE Connect iOS does not have access to the device's Downloads folder, only its own sandboxed Document directory, located in Files App: On My Phone/KDE Connect/
• KDE Connect iOS does not currently use the device's notification center. Without background activity, it wouldn't be very useful. Currently, all statuses and user information are displayed through alerts in the app, which was actually recently revamped by a Seasons of KDE 2022 project. So the only way to "check for more information about the progress" is to keep the app open.
  
  We do have somewhat of a plan to implement the features that are currently lacking from the points above, but we can't say anything for certain at the moment.
  
  Lastly, regarding the other general statement "See how easy it was to transfer files using Wi-Fi? If you want to know more, you can go to the KDE Connect website.":
  
  I believe that KDE Connect doesn't strictly need Wi-Fi to be able to function. As long as a LAN connection can be established between 2 devices, it will work. Meaning it will technically work if 2 devices are connected directly via Ethernet, or if you're VPN or SSH-ing from the other side of the globe.

Hello, @Guilhermems. Thanks for writing up those instructions! It's a nice, quick documentation for all the KDE Connect clients. But I would like to point up a couple of things about the iOS client in particular.

Hi, @apollozhu. Coincidentally, I'm writing a tutorial about sending files with KDE Connect for Promo. I don't have access to an iOS device, so I just assumed the instructions should be similar between Android and iOS. I have just updated the text with iOS instructions. Can you or someone else from KDE Connect check if the instructions I wrote would apply to iOS? The text is here: https://userbase.kde.org/Tips/Transfer_files_between_phone_and_PC_using_Wi-Fi

That's awesome. It would be great if you joined #kde-promo:kde.org to discuss this.

• Promote your App, a tool made by Apple: https://tools.applemediaservices.com/app-store-promote/app/1580245991
  • @apollozhu prefers the "Dark" background, really make the orange icon standout)
• Video demo made by @lucaswzx: https://youtu.be/x3ixd9Fb82A
• Screenshots: https://apps.apple.com/app/kde-connect/id1580245991

After announcing the intention to send KDE Connect iOS to App Store for Apple to review (but not release until we take care of T15319), there were no objections (only suggestion is to do phased release for the actual release)

Neither I or @lucaswzx had time to prepare for this and the TestFlight is full again, we decided to prioritize releasing to App Store instead of getting featured by Apple.

Merged

This is may be covered by the Connectivity Report plugin

Merged https://invent.kde.org/network/kdeconnect-ios/-/merge_requests/60

Created an MR with these changes :)

Merged.

Hi, I opened a PR with this change here: https://invent.kde.org/network/kdeconnect-ios/-/merge_requests/59

Hi, I just opened an MR with this change :)

I have gone through Flowchart 1 (in the Encryption Links box in the lower-left of https://www.bis.doc.gov/index.php/encryption-and-export-administration-regulations-ear ) and end up in the Publicly available end state. The instructions on https://www.ecfr.gov/current/title-15/subtitle-B/chapter-VII/subchapter-C/part-742/section-742.15 say "send an email", so that seems like a safe thing to do. Something along the lines of "for authentication (pairing) only, and the source is available at some-KDE-invent-location". I'm counting on the KDE Connect people to accurately characterize the use of crypto in the application. You might have to answer no specifically here, unless you've determined exemption (c) applies, so that you can see if the other not-required cases pop up later in the form.

Export Compliance Information
Does your app qualify for any of the exemptions provided in Category 5, Part 2 of the U.S. Export Administration Regulations?

• Yes
• No

Make sure that your app meets the criteria of the exemption listed below. You are responsible for the proper classification of your product. Incorrectly classifying your app may lead to you being in violation of U.S. export laws and could make you subject to penalties, including your app being removed from the App Store.

You can select Yes for this question if the encryption of your app is:
(a) Specially designed for medical end-use
(b) Limited to intellectual property and copyright protection
(c) Limited to authentication, digital signature, or the decryption of data or files
(d) Specially designed and limited for banking use or “money transactions”; or
(e) Limited to “fixed” data compression or coding techniques

You can also select Yes if your app meets the descriptions provided in Note 4 for Category 5, Part 2 of the U.S. Export Administration Regulations.