RocketChat / RocketChat/Rocket.Chat
How to load Rocket.Chat inside an iframe in Webview iOS
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 46.1k
- Forks
- 13.9k
- Avg merge
- 3d 3h
- Merged PRs (30d)
- 130
Description
Description:
Rocketchat using iframe loads normally in android webview, but does not load in ios wkwebview.
(*Even if you load the rocketchat channel directly into wkwebview, the same error occurs and it does not work.)
Steps to reproduce:
1.The domain on which rocketchat is running is abc.com
-
The site where rocketcat will be inserted using an iframe is call.com.
-
Use the iframe tag on the call.com web page to load the rocketchat website installed on abc.com.
4.Load the call.com webpage into iOS wkwebview.
When loading, an error occurs in 2 lines in console.log and no progress is made.
It loads normally in browsers such as pc chrome, android chrome, android webview, and ios safari, but does not work properly only in ios WKWebView.
Server Setup Information:
iOS : 17.2
Rocketchat : 6.3.10
Nodejs : 14.21.3
OS: Centos 7.9
MongoDB : 5.0.22
Error Message(console.log)
*TypeError: Cannot call a class constructor without new
*There is no route for the path:"/channel/channelName/?layout=embedded"
Error Screenshots
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the iframe and direct-channel cases in an iOS 17.2 WKWebView using the versions listed in the issue, then compare the console errors with the working browser and Android cases. Done means identifying a supported loading path or a confirmed Rocket.Chat fix for the constructor and missing-route errors.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- ios, typescript
- Domain
- mobile, web-dev
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100