ShenQi

通讯录权限维护说明

当前 iOS App 的通讯录权限获取逻辑没有被代码屏蔽，但是否真正触发，受服务端配置控制。

• 当前代码常量 NowUserId 为 279
• 配置接口为 GET https://api.liulao.top/api/system/applicationConf?userId=279
• 2026-05-14 核对结果：
  • contactApplyMode = 1
  • isUse = 1
• 结论：
  • 当前线上配置下，通讯录权限申请是开启状态
  • 如果后续后台把 contactApplyMode 改成非 1，代码会跳过通讯录权限申请和联系人上传流程

相关代码位置：

• ShenQi/MacroDefine.h
  • NowUserId
  • ConfigURL
  • ContactsURL
• ShenQi/LaunchViewController.m
  • 拉取配置后，如果 contactApplyMode == 1，会调用 AppDelegate 的权限检查逻辑
• ShenQi/AppDelegate.m
  • applicationDidBecomeActive:
  • setupAlertContact
  • 负责首次权限申请和拒绝后的设置页弹窗提醒
• ShenQi/MainOldViewController.m
  • setupAddContactData
  • refreshMayknowFriendData
  • uploadContactsData:
  • 负责在主页面进入后读取联系人并上传到 /api/customer/customers
• ShenQi.xcodeproj/project.pbxproj
  • 已配置 NSContactsUsageDescription

排查建议：

1. 先确认 NowUserId 是否被改动。
2. 再请求配置接口，确认 contactApplyMode 当前值。
3. 如果 contactApplyMode == 1 但设备仍不弹权限框，再检查设备是否已经拒绝过权限，以及系统设置里该 App 的通讯录权限状态。

Icon Hide Notes

This project currently hides the home2 and noti2 menu icons by commenting out their menu registration code.

File location:

• ShenQi/MainOldViewController.m

Commented code location:

• In - (void)viewDidLoad, inside the menuArray build section.
• home2 hide code:
  • height = height + 60;
  • LinkConfig *config = [[LinkConfig alloc] init];
  • config.isGoBack = YES;
  • config.icon = @"home2";
  • config.name = @"HOME2";
  • config.linkUrl = appDelegate.mainURLString;
  • [menuArray addObject:config];
• noti2 hide code:
  • height = height + 70;
  • [menuArray addObject:[NSNumber numberWithInteger:DSWebMenuNotiType]];

Why it does not show now:

• home2 and noti2 are only displayed after being added into menuArray.
• The add-to-menuArray code is commented out, so they are not rendered when entering the app.

How to restore later:

1. Open ShenQi/MainOldViewController.m.
2. Find the // 回到主页 block and uncomment the home2 related lines.
3. Find the // 推送中心按钮 block and uncomment the noti2 related lines.
4. Keep the matching height = ... lines restored together, otherwise the menu height will be inconsistent.

Current change date:

• 2026-04-30

可以把app的这个按钮去掉吗? 苹果和安卓

WE1WIN - we1win.hfcapital.top U8888AUD - u88.hfcapital.top AFB77AU - afb77au.hfcapital.top GG66au - gg66au.hfcapital.top BB8AU - bb8au.hfcapital.top BE9AU - be9au.hfcapital.top UU33AU - uu33au.hfcapital.top AA7AU - www.aa7au.top BNG1AU - www.bng1au.top XOXOAU8 - xoxau.mgmhotram.top

Getting started

To make it easy for you to get started with GitLab, here's a list of recommended next steps.

Already a pro? Just edit this README.md and make it your own. Want to make it easy? Use the template at the bottom!

Add your files

• Create or upload files
• Add files using the command line or push an existing Git repository with the following command:

cd existing_repo
git remote add origin https://gitlab.dengshikj.com/all/shenqi.git
git branch -M main
git push -uf origin main

Integrate with your tools

• Set up project integrations

Collaborate with your team

• Invite team members and collaborators
• Create a new merge request
• Automatically close issues from merge requests
• Enable merge request approvals
• Automatically merge when pipeline succeeds

Test and Deploy

Use the built-in continuous integration in GitLab.

• Get started with GitLab CI/CD
• Analyze your code for known vulnerabilities with Static Application Security Testing(SAST)
• Deploy to Kubernetes, Amazon EC2, or Amazon ECS using Auto Deploy
• Use pull-based deployments for improved Kubernetes management
• Set up protected environments

---

Editing this README

When you're ready to make this README your own, just edit this file and use the handy template below (or feel free to structure it however you want - this is just a starting point!). Thank you to makeareadme.com for this template.

Suggestions for a good README

Every project is different, so consider which of these sections apply to yours. The sections used in the template are suggestions for most open source projects. Also keep in mind that while a README can be too long and detailed, too long is better than too short. If you think your README is too long, consider utilizing another form of documentation rather than cutting out information.

Name

Choose a self-explaining name for your project.

Description

Let people know what your project can do specifically. Provide context and add a link to any reference visitors might be unfamiliar with. A list of Features or a Background subsection can also be added here. If there are alternatives to your project, this is a good place to list differentiating factors.

Badges

On some READMEs, you may see small images that convey metadata, such as whether or not all the tests are passing for the project. You can use Shields to add some to your README. Many services also have instructions for adding a badge.

Visuals

Depending on what you are making, it can be a good idea to include screenshots or even a video (you'll frequently see GIFs rather than actual videos). Tools like ttygif can help, but check out Asciinema for a more sophisticated method.

Installation

Within a particular ecosystem, there may be a common way of installing things, such as using Yarn, NuGet, or Homebrew. However, consider the possibility that whoever is reading your README is a novice and would like more guidance. Listing specific steps helps remove ambiguity and gets people to using your project as quickly as possible. If it only runs in a specific context like a particular programming language version or operating system or has dependencies that have to be installed manually, also add a Requirements subsection.

Usage

Use examples liberally, and show the expected output if you can. It's helpful to have inline the smallest example of usage that you can demonstrate, while providing links to more sophisticated examples if they are too long to reasonably include in the README.

Support

Tell people where they can go to for help. It can be any combination of an issue tracker, a chat room, an email address, etc.

Roadmap

If you have ideas for releases in the future, it is a good idea to list them in the README.

Contributing

State if you are open to contributions and what your requirements are for accepting them.

For people who want to make changes to your project, it's helpful to have some documentation on how to get started. Perhaps there is a script that they should run or some environment variables that they need to set. Make these steps explicit. These instructions could also be useful to your future self.

You can also document commands to lint the code or run tests. These steps help to ensure high code quality and reduce the likelihood that the changes inadvertently break something. Having instructions for running tests is especially helpful if it requires external setup, such as starting a Selenium server for testing in a browser.

Authors and acknowledgment

Show your appreciation to those who have contributed to the project.

License

For open source projects, say how it is licensed.

Project status

If you have run out of energy or time for your project, put a note at the top of the README saying that development has slowed down or stopped completely. Someone may choose to fork your project or volunteer to step in as a maintainer or owner, allowing your project to keep going. You can also make an explicit request for maintainers.